Connecting ecommerce, marketplaces, WMS and EDI to Unleashed: a practical guide

A Shopify or WooCommerce store here. A marketplace or two. A 3PL or warehouse system somewhere else. Xero or QuickBooks on top. And, for many wholesalers and brands, a retailer or two with their own EDI document requirements.

Unleashed does its job well. The storefront does its job well. The problem is the gap between them, and in most growing businesses that gap is filled by a person: copying orders across every morning, updating stock by hand, typing tracking numbers back into the store, keying retailer purchase orders into Unleashed from a portal.

We call that the manual middle. It is slow, it is error-prone and it scales badly. What works for one channel does not work for five. What works for one warehouse does not survive the move to a second.

Keep Unleashed at the centre

The pattern that works is simple to describe: Unleashed stays the operational hub for orders, stock, products, customers and purchasing, and everything else connects to it.

• Orders arrive from storefronts, marketplaces and retailers and become Unleashed sales orders.
• Stock leaves Unleashed and updates every channel.
• Fulfilment instructions go to the warehouse, and despatch confirmations come back.
• Tracking, despatch advice and invoices go out to whoever needs them.

The reason this is hard in practice is that the systems around Unleashed do not speak the same language. A Shopify store speaks webhooks and APIs. A 3PL may speak CSV files over SFTP. A retailer speaks EDIFACT or Tradacoms over AS2. A connector that only handles one of those leaves you with three integrations to own, three sets of logs to check and three suppliers to chase.

Supply Lens handles all of them on one platform. Every document, whatever its source format, is converted into a single canonical format, has the right business rules applied and is created in the shape the destination system expects. Because every connector speaks that same format, connecting a system once makes every relevant flow available against it.

Why standard connectors and custom builds both struggle

There are broadly three ways Unleashed businesses try to close the gap.

Marketplace connector apps are quick to switch on and work well for simple setups. They tend to stop working when the business meets a scenario they were not designed for: bundles, multiple warehouses, batch-tracked stock, B2B pricing, a new channel, or a trading partner that changes its document format. At that point the connector becomes a maintenance burden nobody owns.

Custom development can handle anything, but it takes months, costs significantly and becomes difficult to support once the original developer moves on.

Generic iPaaS platforms are flexible but slow to deploy, and they rarely come with the commerce, fulfilment and EDI knowledge that makes an Unleashed integration behave correctly.

Supply Lens sits in the space between: prebuilt Unleashed patterns covering the common ground, configurable business logic on top and bespoke extension for what is genuinely unique to your operation. Rules can change, channels can be added and trading partners onboarded without rebuilding from scratch.

1. Ecommerce storefronts to Unleashed

Shopify to Unleashed is the most repeatable connected-commerce pattern there is, and WooCommerce follows the same shape. Supply Lens also connects Magento (Adobe Commerce), BigCommerce, Wix, Squarespace, Square and several others.

What the integration does

Orders in. Eligible storefront orders create sales orders in Unleashed automatically, with customer, delivery address, shipping charges, tax treatment and order reference mapped consistently. No rekeying.

Stock out. Stock levels in Unleashed update the storefront in near real time. The figure sent is Unleashed's available quantity (physical stock net of allocations), not quantity on hand, because a channel selling live stock needs to know what can actually be sold.

Fulfilment back. When a despatch is created in Unleashed, tracking is pushed back to the storefront and the order is fulfilled. The customer gets their despatch email with the tracking link in it.

Optional flows sit alongside: price sync from Unleashed price tiers, product data flows, multi-location stock logic, different rules per store or sales channel and separate handling for B2B and direct-to-consumer orders.

The details that make or break it

Despatch is the trigger, not order status. The Unleashed sales shipment is the natural fulfilment event. Integrations that key off order status alone get partial shipments and multi-parcel orders wrong.

Product matching. Products are matched by SKU, with barcode or a custom field as the fallback where catalogues differ. Where a channel uses a different code for the same product, alternate SKU mapping handles the equivalence.

Bundles and kits. Decide early whether stock is tracked at bundle or component level. Component-level handling is the proven pattern, particularly given the constraints Shopify's order APIs have around bundle variants.

Batch and serial tracking. If any product in the range is batch or serial tracked, it has to be designed into the despatch flow from day one. Retrofitting it into a live integration is significantly more work than including it at the start.

WooCommerce plugins. WooCommerce stores vary far more than Shopify stores. Checkout field plugins, tax plugins and shipment tracking plugins all change what an order looks like, so it is worth confirming which plugins touch orders before configuration begins. Sequencing matters too: tracking is posted before the order status changes, so the Completed Order email goes out with tracking included rather than without it.

High order volumes into finance. Busy stores can push more invoices into Xero or QuickBooks than is sensible. A consolidated invoicing pattern protects the finance system and keeps the ledger readable.

2. Marketplaces to Unleashed

Wholesalers and brands rarely sell through one channel. A direct storefront, a set of marketplaces and a handful of retail partners each bring their own data format and operational rules, and they all draw on the same stock.

Supply Lens connects marketplaces into Unleashed alongside your storefront, including eBay, Etsy, TikTok Shop, Temu, Wayfair, OnBuy, Notonthehighstreet, Tesco Marketplace, Wish and Yumbles, Mirakl-powered marketplaces and wholesale marketplaces such as Faire and JOOR. Rithum (formerly CommerceHub and ChannelAdvisor) is supported for dropship and marketplace orders, as are retailer dropship programmes including Dunelm, The Range, Smyths Toys, Holland & Barrett, Freemans and Virtualstock.

How marketplace flows work with Unleashed

Marketplace orders arrive in Unleashed as sales orders, exactly as storefront orders do, so your team works one order queue rather than one per channel. Where the marketplace supports it, stock is synced back from Unleashed and despatch tracking is returned to the buyer.

The points to get right are the same ones that trip up single-channel setups, multiplied:

• One stock pool, many channels. Every channel reads from Unleashed available stock, so an order on one channel is reflected everywhere else on the next sync.
• Per-channel identifiers. Marketplaces often carry their own product codes. A cross-reference per channel keeps Unleashed SKUs clean.
• Per-channel rules. Customer account strategy, tax, shipping charges and warehouse routing can differ by channel without separate integrations.
• Dropship programmes behave like EDI. Retailer dropship portals usually expect order acknowledgements and despatch confirmations on their own terms, so they are handled with the same discipline as a retailer EDI connection.

3. 3PL and WMS integration with Unleashed

When fulfilment is outsourced, the warehouse becomes the operational truth for despatch, tracking and often inventory, while Unleashed remains the system of record for orders and stock. The integration has to manage a genuine two-way flow.

The four core flows

Order handoff. When a sales order in Unleashed is ready for fulfilment, it is formatted for the warehouse and sent, by API or by file. The warehouse reference comes back and is preserved against the Unleashed order.

Despatch confirmation. When the warehouse picks, packs and despatches, a shipment is created in Unleashed, including batch data where batch tracking applies. That shipment then drives tracking back to the storefront or marketplace. One integration, end to end.

Goods inbound. When a purchase order is raised in Unleashed, it is sent to the warehouse as an expected delivery.

Goods receipt. When the warehouse receives the stock, the receipt comes back and receipts the purchase order lines in Unleashed, with batches reconciled before anything is posted.

API warehouses and file-based 3PLs

Some warehouse platforms have well-documented APIs. Many 3PLs still exchange structured CSV files over SFTP. Supply Lens supports both, using a consistent document model across each, and connects providers including Mintsoft, ShipBob, ShipHero, Logiwa, VeraCore, Descartes Peoplevox, ClarusWMS, Codestorm, Despatch Cloud, Zendbox, James and James, THG and a long list of file-based 3PLs. Shipping platforms such as Sendcloud and ShipStation are connected in the same way.

What to plan for

4. Retailer EDI integration with Unleashed

Retailer EDI is where Supply Lens started, and it remains a core strength. The objective is straightforward: turn retailer purchase orders into Unleashed sales orders, and return the compliance documents the retailer requires, without your team or Unleashed needing to understand EDI.

In practice, retailer EDI is notoriously specific. Each retailer has its own codes, document structures, mandatory fields and tolerance rules, and the penalty for getting them wrong is chargebacks, rejected invoices and strained trading relationships.

The EDI document cycle

Purchase order in. The retailer's order is received over the EDI network, validated, translated and created as a sales order in Unleashed.

Acknowledgement out. An order acknowledgement is generated and sent back to the retailer.

Despatch advice out. When the order is despatched in Unleashed, an ASN or despatch advice is built with the retailer's specific formatting and transmitted.

Invoice out. Invoice data from Unleashed is transformed into the retailer's invoice format, with line tolerances and mandatory fields enforced, and sent.

The translation layer

The hard part of EDI is not the transport; it is the cross-referencing. Retailer documents carry codes that bear no resemblance to your internal references. Supply Lens maintains the translation for:

• Retailer barcodes and product codes to Unleashed SKUs
• Depot, delivery location and supplier codes
• Customer and party identifiers, including GLNs
• Warehouse and entity routing per trading partner

Supply Lens assigns and manages GLNs as part of enablement. If you already trade by EDI under an existing GLN, share it early so the migration can be planned around it and retailer continuity maintained.

Onboarding trading partners safely

Each new trading partner runs in a test state, per document type, until end-to-end testing passes. New partners are added to a live setup without disturbing the connections already running. Where a document fails, whether from an unknown code, an ambiguous location or a quantity outside tolerance, it lands in an exception queue with a notification and a clear resolution path rather than disappearing.

Supply Lens runs 50+ UK retailer EDI connections over AS2, SFTP and FTP, covering grocery, convenience, health and beauty, DIY and builders' merchants, department stores and wholesale, including Tesco (EDIFACT and Tradacoms), Sainsbury's, Asda, Morrisons, Co-op, Waitrose, Ocado, Boots, Marks & Spencer, John Lewis and Amazon Vendor Central across the UK, Europe and the Middle East.

Getting the Unleashed details right

Across all four areas, a handful of Unleashed realities shape how an integration should be designed. They are worth knowing whoever builds yours.

Sandbox and production share one endpoint. Which environment a request reaches is decided entirely by the API credentials. Test-to-live promotion is clean: swap credentials, nothing else changes.

Available versus on hand. Unleashed distinguishes available quantity from quantity on hand. Channels should receive available. Warehouse and volume reporting usually wants on hand. Every stock flow should state which figure it uses.

Built to recover on its own. Sync is near real time, typically within minutes. Every integration is built with automatic retries, idempotent sync (a failed run can simply run again) and full logging, which protects you from the transient API disruptions every cloud platform has from time to time.

Look records up, do not store links. Supply Lens resolves records by the identifier it is given (SKU, customer code) on every run rather than storing cross-system IDs. If a record is deleted and recreated, the next sync finds it again instead of breaking the link.

You can see what is flowing. Every transaction is visible and searchable, with the payload sent and the payload returned, so any discrepancy can be traced to its source in minutes rather than argued about for days.

What to have ready before you start

The fastest projects are the ones where the discovery questions are answered up front. Depending on which flows you need, have these to hand:

• Credentials: Unleashed API access, plus storefront, marketplace or warehouse API credentials, or SFTP details and file specifications for file-based 3PLs.
• Warehouses: your Unleashed warehouse list with names and codes, and which warehouse serves which channel.
• Products: sample SKUs from both sides, and confirmation of which product ranges are batch or serial tracked.
• Orders: representative sample orders, including bundles, discounts and variable products if you sell them.
• Shipping: your shipping methods and how they map to Unleashed charges or warehouse service codes.
• EDI: document specifications or sample files per retailer, your Customer Assigned and Supplier Assigned Codes, any existing GLN and product and depot cross-references.
• A named tester: someone on your side who knows the operation and can sign off each flow in testing.

Frequently asked questions

Connect your Unleashed operation

If your team is rekeying orders into Unleashed, going live on a new channel, adding a 3PL, or facing a retailer's EDI requirements, Supply Lens can take the manual middle out of your operation, with 175+ prebuilt connectors and Unleashed kept firmly at the centre.