Connect BigCommerce to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between BigCommerce and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with BigCommerce EDI
XEDI connects BigCommerce with retailer EDI so wholesale orders arrive against the right customer groups and price lists, and despatch confirmations and invoices go back out without re-entry.
One managed platform, no custom code
XEDI maps BigCommerce to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Price lists make wholesale workable, provided the order finds the right one
BigCommerce handles differentiated pricing through customer groups and price lists, which suits wholesale well. A retailer belongs to a group, that group sees a price list, and an order from them should price from it automatically.
The integration's job is making sure an EDI order actually resolves that way. It arrives carrying the retailer's own item codes and their expected prices, and if it lands against the wrong group the order is created at a number neither party agreed to.
Variants are where retailer identifiers stop matching
A retailer sends a GTIN for a specific pack of a specific product. In BigCommerce that is usually a variant, and variants are where SKU conventions get loose: option combinations, legacy codes, items created for a campaign and never tidied.
The mapping resolves each retailer's identifier to the variant that actually ships, at each packaging level they order in. Getting it wrong does not throw an error, it ships the wrong thing.
What your team sees day to day
You get an EDI mailbox and a portal that works like an inbox, so retailer orders arrive apart from your consumer traffic.
What shipped becomes the despatch advice, adjusted where the delivery moved, carrying SSCC labels at pallet level, and the invoice follows delivery with its arrival confirmed in the dashboard.
The integration sits over that workflow and automates it, so orders are created in BigCommerce and shipments raise the outbound documents. Smaller sellers run the portal alone; our API is there for finer requirements.
Documents you can exchange
- Retailer orders landing as BigCommerce orders
- Order acknowledgements returned to the retailer
- Despatch advice and ASN messages from shipments
- Invoices raised against the shipment
- Price list and catalogue data where a retailer requires it
Built for BigCommerce teams
Whoever owns BigCommerce in your business, XEDI keeps EDI accurate and hands-off.
- Brands selling direct and wholesale
- Ecommerce managers
- Operations and fulfilment teams
- Finance teams handling wholesale invoicing
- Businesses adding retail alongside online sales
BigCommerce EDI document types
These are the wholesale flows; your consumer storefront is unaffected.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand creating a BigCommerce order against the right customer group and price list. | Retailer to BigCommerce |
| Order acknowledgements | What will be supplied once stock is committed, including lines short or substituted. | BigCommerce to retailer |
| Advanced shipping notices | Pallet and carton detail from the shipment, with SSCC labels for the retailer's goods-in. | BigCommerce to retailer |
| Invoices | Raised against the shipment and referenced so the retailer can match them without intervention. | BigCommerce to retailer |
| Credit notes | Adjustments against the invoice being corrected, where a delivery falls short. | BigCommerce to retailer |
| Price list and catalogue data | Product, variant and price data published where a retailer maintains a catalogue. | BigCommerce to retailer |
How to connect BigCommerce with EDI using XEDI
Most of the work is resolving retailer identifiers to variants and orders to the right price list. The sequence below is what onboarding looks like from your side.
-
01
We scope which BigCommerce storefronts, customer groups and price lists carry wholesale.
-
02
We build the mapping between each retailer's documents and your products, variants and price lists.
-
03
We configure validation so an order is checked against the retailer's terms before a BigCommerce order exists.
-
04
We prove the order, shipment and invoice flows against what each retailer requires and against how your store is set up.
-
05
You get wholesale arriving at the right price, and we keep it correct as your catalogue changes.
Ready to connect BigCommerce?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about BigCommerce EDI
Common requirements
- BigCommerce store and API credentials
- Customer group and price list structure
- Product and variant identifiers
- Shipment and fulfilment rules
- The trading partners you deal with, or plan to
What we need from you to build it
Only what we cannot hold for you. Retailer requirements are already ours; what we need is how your store prices wholesale.
- BigCommerce access
- Store API credentials with rights to orders, products, customers and shipments.
- Customer group and price list structure
- Which group each retailer belongs to and which price list it sees, since pricing resolves through them.
- Product and variant identifiers
- Variants against retailer GTINs at each packaging level, including anything created ad hoc and never tidied.
- Fulfilment rules
- How shipments are recorded and what the retailer expects to see for part deliveries.
- Which retailers you supply
- Who you sell to wholesale, now and next. We already hold what each of them expects.
Why suppliers choose XEDI for BigCommerce
- Most retailers are on our network already, so a wholesale account can be trading before the price list mapping is agreed.
- Orders resolve to the right customer group and price list, so a wholesale order is not created at consumer pricing.
- Retailer identifiers are mapped to the variant that actually ships, which is where loose SKU conventions cause silent errors.
- A new wholesale customer is our build rather than a change to your storefront.
- SSCC labels and pallet detail are produced to each retailer's format from the actual shipment.
- If a retailer raises a problem it comes to us, and we resolve it before it affects payment.
Can BigCommerce handle wholesale pricing for EDI orders?
Yes, through customer groups and price lists. The integration makes sure an EDI order resolves to the right group so it prices from the list agreed with that retailer rather than from consumer pricing.
How are retailer item codes matched to our products?
Each retailer's identifiers are mapped to the variant that actually ships, at each packaging level they order in. That mapping is maintained by us as your catalogue changes.
Do we need a separate store for wholesale?
Usually not. Wholesale arrives separately and is handled to the retailer's requirements, while your consumer storefront carries on unchanged.
Plan your BigCommerce EDI setup
Everything you need to scope, map and go live with BigCommerce, in one place.