Skip to content

Channel

Fanatics (Legacy ISA ID: SPSFANATICSP)

Plan a reliable EDI exchange for Fanatics (Legacy ISA ID: SPSFANATICSP). Explore 7 document references, map them to your business records and test the complete workflow before launch.

Documents
7 transactions
Standards
X12
Implementation
Mapping and launch plan

Implementation guide

Fanatics (Legacy ISA ID: SPSFANATICSP): EDI implementation plan

Build a reliable EDI workflow for Fanatics (Legacy ISA ID: SPSFANATICSP). Use 7 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 856 Ship Notice ManifestListed for Fanatics (Legacy ISA ID: SPSFANATICSP) 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 810 InvoiceListed for Fanatics (Legacy ISA ID: SPSFANATICSP) 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 850 Purchase OrderListed for Fanatics (Legacy ISA ID: SPSFANATICSP) 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 860 Purchase Order Change Request Buyer InitiatedListed for Fanatics (Legacy ISA ID: SPSFANATICSP) 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.
X12 855 Purchase Order AcknowledgmentListed for Fanatics (Legacy ISA ID: SPSFANATICSP) purchase-order response

original purchase order, response revision and order line

  • Test a partially accepted order with a backordered line and retain both outcomes.
  • Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates.
X12 180 Return Merchandise Authorization And NotificationListed for Fanatics (Legacy ISA ID: SPSFANATICSP) return authorization

return authorization, original order and returned item

  • Test a return quantity larger than the original shipment and require review.
  • Keep authorization separate from physical receipt so stock is not increased early.
X12 846 Inventory Inquiry AdviceListed for Fanatics (Legacy ISA ID: SPSFANATICSP) 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.

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 Fanatics (Legacy ISA ID: SPSFANATICSP). Compare other Fanatics channels before reusing a mapping.

  2. Map records and assign owners

    Start with shipment notice (ASN), accounts-receivable or accounts-payable invoice, purchase order or sales order. 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 Fanatics production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using shipment, order, package and item references. 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 flow on this channel

Document relationships on Fanatics (Legacy ISA ID: SPSFANATICSP)

This channel lists all 7 document types in the Fanatics 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 Fanatics (Legacy ISA ID: SPSFANATICSP)
  2. 846 Inventory Inquiry Advice
  3. 852 Product Activity Data not listed on Fanatics (Legacy ISA ID: SPSFANATICSP)

Fanatics (Legacy ISA ID: SPSFANATICSP) questions

Which EDI documents are listed for Fanatics (Legacy ISA ID: SPSFANATICSP)?

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

How should I choose the Fanatics EDI channel?

Fanatics (Legacy ISA ID: SPSFANATICSP) lists 7 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 Fanatics mapping preserve?

For X12 856 Ship Notice Manifest, plan around shipment, order, package and item references. For X12 810 Invoice, use invoice number, purchase order and invoice line. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean Fanatics 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 Fanatics (Legacy ISA ID: SPSFANATICSP) EDI?

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. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Connect Fanatics 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.