Skip to content

Channel

BASS PRO DSCOBass Pro - Dropship via DSCO

Plan a reliable EDI exchange for BASS PRO DSCO / Bass Pro - Dropship via DSCO. Explore 5 document references, map them to your business records and test the complete workflow before launch.

Book an EDI demo ← All BASS PRO DSCO channels
Documents
5 transactions
Standards
X12
Implementation
Mapping and launch plan

Implementation guide

BASS PRO DSCO / Bass Pro - Dropship via DSCO: EDI implementation plan

Build a reliable EDI workflow for BASS PRO DSCO / Bass Pro - Dropship via DSCO. Use 5 document types to plan record mapping, prevent duplicate processing and reconcile results in your business systems.

The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
X12 850 Purchase OrderListed for Bass Pro - Dropship via DSCO purchase order or sales order

buyer purchase order, order line and trading-party identifiers
  • Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit.
  • Resend one purchase order and confirm that only one sales order is created.
X12 846 Inventory Inquiry AdviceListed for Bass Pro - Dropship via DSCO inventory availability record

item, location, quantity type and snapshot time
  • Distinguish on-hand, available and reserved quantities before publishing availability.
  • Deliver an old snapshot after a new one and prevent stale stock from replacing current values.
X12 810 InvoiceListed for Bass Pro - Dropship via DSCO accounts-receivable or accounts-payable invoice

invoice number, purchase order and invoice line
  • Reconcile line amounts, allowances, charges and tax to the invoice total.
  • Submit the same invoice twice and verify that it cannot create a second payable.
X12 856 Ship Notice ManifestListed for Bass Pro - Dropship via DSCO shipment notice (ASN)

shipment, order, package and item references
  • Reconcile item quantities through shipment, order and packaging levels against the physical shipment.
  • Test split shipments for one purchase order and prevent the second ASN from replacing the first.
X12 860 Purchase Order Change Request Buyer InitiatedListed for Bass Pro - Dropship via DSCO buyer order-change request

original purchase order, change revision and affected line
  • Apply a quantity reduction to the existing order instead of creating another order.
  • Test a cancellation arriving after allocation or shipment and route it to an exception owner.

Implementation steps

  1. Choose the trading account and channel

    Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Bass Pro - Dropship via DSCO. Compare other BASS PRO DSCO channels before reusing a mapping.

  2. Map records and assign owners

    Start with purchase order or sales order, inventory availability record, accounts-receivable or accounts-payable invoice. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.

  3. Test a complete exchange

    Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the BASS PRO DSCO production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using buyer purchase order, order line and trading-party identifiers. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.

Go-live checklist

  • The required X12 documents, versions and sample files are agreed.
  • Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
  • Delivery receipts, document validation and business responses have monitoring and a named owner.
  • Tests cover duplicates, partial processing and reconciliation with realistic business records.

Document catalog

EDI documents listed for BASS PRO DSCO / Bass Pro - Dropship via DSCO

5 EDI transactions listed in this catalog.

Document flow on this channel

Document relationships on Bass Pro - Dropship via DSCO

This channel lists all 5 document types in the BASS PRO DSCO directory. Example relationships are shown below; confirm the required sequence in the channel guide.

Catalog & inventory

Some example steps listed
  1. 832 Price / Sales Catalog not listed on Bass Pro - Dropship via DSCO
  2. 846 Inventory Inquiry Advice
  3. 852 Product Activity Data not listed on Bass Pro - Dropship via DSCO

Network onboarding

Plan the Rithum connection

The directory associates Rithum with 23 partner entries across 25 channels. Confirm transport, network enrollment, commercial terms and testing with the channel owner before implementation.

Most frequently listed documents on Rithum
  • 850 25 ch
  • 856 25 ch
  • 846 24 ch
  • 810 20 ch
  • 870 10 ch
  • 855 8 ch
Other partner entries associated with Rithum

Bass Pro - Dropship via DSCO questions

Which EDI documents are listed for BASS PRO DSCO / Bass Pro - Dropship via DSCO?

X12 850 Purchase Order; X12 846 Inventory Inquiry Advice; X12 810 Invoice; X12 856 Ship Notice Manifest; X12 860 Purchase Order Change Request Buyer Initiated. Confirm which documents, directions and versions apply to your account.

How should I choose the BASS PRO DSCO EDI channel?

Bass Pro - Dropship via DSCO lists 5 distinct document types. Match the channel to your business unit, account and delivery arrangement; compare the other channel links before choosing a connection. Confirm access and enrollment with the channel owner.

Which identifiers should the BASS PRO DSCO mapping preserve?

For X12 850 Purchase Order, plan around buyer purchase order, order line and trading-party identifiers. For X12 846 Inventory Inquiry Advice, use item, location, quantity type and snapshot time. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean BASS PRO DSCO accepted the business document?

Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.

What should be tested before launching BASS PRO DSCO / Bass Pro - Dropship via DSCO EDI?

Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit. Resend one purchase order and confirm that only one sales order is created. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Connect BASS PRO DSCO EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.

Book an EDI demo Explore the EDI platform