European Fulfilment and Delivery

Every order into Seabourne.
Every despatch back out.

Seabourne holds your stock and ships your orders across the UK and Europe. Supply Lens gets orders there from wherever they originate: Shopify, an ERP like Unleashed or Enterpryze, a marketplace or an EDI trading partner. Despatch confirmations and tracking come back to your ERP, storefront and customers automatically.

Seabourne data flows Supply Lens integration layer
Orders in from any source
Shopify / ERP / Marketplace any source
Seabourne
SKUs · quantities · delivery detail data passed
Pick, pack and despatch
Despatch confirmations back
Carrier · tracking · despatch date shipment
ERP / Storefront / Customer
Stock levels cost
ERP / Storefront
Carriers used Royal Mail DPD Evri UPS FedEx DHL + more
The flows in detail

Orders in. Stock and despatches back.
Everything in between automated.

Seabourne's job is to hold your stock and get orders delivered across multiple countries. Supply Lens's job is to make sure every order arrives with everything Seabourne needs to pick it, and that every despatch event flows back without human input.

Orders in
Any source → Seabourne

Seabourne needs orders to pick. Supply Lens sends them from wherever they originate: Shopify, an ERP like Unleashed or Enterpryze, a marketplace like eBay or Amazon, an EDI trading partner or any other connected system. Each order is transformed into the format Seabourne expects: delivery address, product lines, quantities and the item-level detail Seabourne needs to pick the order correctly.

This is not a simple order pass-through. The right information has to travel with the order. Bundles have to arrive as the components Seabourne actually picks, delivery service has to map to what Seabourne offers, and every SKU has to resolve to the code held in their system. Supply Lens ensures that every order arrives with the weight, dimensions, declared value and any custom field data that your rules are built around. An order that arrives without those fields won't route correctly regardless of how well your rules are written.

Shopify orders ERP sales orders Marketplace orders EDI orders Bundles exploded to components Delivery service mapped Custom field mapping SKU cross-reference
Shopify / ERP / Marketplace
Supply Lens (transform + enrich)
Seabourne order
Stock and despatches back
Seabourne → everywhere

When Seabourne creates a shipment (carrier selected, label printed, consignment created), Supply Lens picks up the shipment event and distributes it to every system that needs to know about it. The ERP sales order is marked as despatched. The Shopify fulfilment is created with the carrier name and tracking number. The customer notification fires. Where the order originated from a marketplace, the fulfilment is confirmed back to that channel.

Stock levels is also returned. When Seabourne confirms the actual cost charged by the carrier for a shipment, Supply Lens passes that cost back to your ERP or finance system. This means your sales margins and shipping cost analysis reflect what was actually charged, not an estimate, without any manual data entry.

ERP despatch update Shopify fulfilment creation Tracking to customer Marketplace fulfilment confirm Stock levels returned Carrier and tracking recorded Partial despatches handled
Seabourne despatch
Supply Lens (distribute)
ERP + Shopify + Channels
Stock and SKU accuracy

Seabourne holds the stock.
Supply Lens keeps the numbers honest.

A third party holding your stock means two systems both believe they know what you have. Supply Lens keeps them agreed: despatches decrement your ERP as they happen, inbound receipts increase it, and the available figure your channels publish reflects what Seabourne can actually ship. So the right carrier is selected automatically every time.

Example stock movements
Event → What Supply Lens updates
Weight
Under 2 kg · UK
Selected
Royal Mail 48
Weight + Service
2–10 kg · next day
Selected
DPD Next Day
Destination
International · declared value > £150
Selected
DHL Express
Channel + Weight
B2B channel · pallet orders
Selected
Pallet courier
Product type
Fragile flag set
Selected
UPS Fragile handling

Rules are configured and maintained in Seabourne. Supply Lens applies each movement as it happens, so your ERP and your channels track what Seabourne is holding rather than what they were last told.

Data Supply Lens passes to Seabourne
Item weight & dimensions
Per-line item weight and dimensions sourced from your ERP or product data. Aggregated to order level or passed per line depending on your Seabourne configuration.
Delivery service mapped
Order value passed through correctly so rules based on insured or declared value thresholds fire as expected, particularly relevant for international shipments.
Source channel & order tags
The originating channel (Shopify DTC, B2B ERP, eBay, Amazon, EDI) is passed as a custom field so channel-specific carrier rules apply. Order tags and flags from the source system are carried through.
Product-level flags
Fragile, hazardous, temperature-controlled or any other product attribute stored in your ERP can be mapped to a Seabourne custom field and used to drive carrier or service selection for those specific items.
Requested service level
Where an order specifies a shipping method (standard, express, next day), that preference is mapped to a Seabourne service level and passed with the order so the correct tier of rule applies.
Where Seabourne integrations break

The rules don't fire if the
data isn't there.

Most Seabourne integration problems aren't connection problems. They're data problems. The order arrives but the SKU does not resolve, the bundle was never exploded, or the delivery service does not map to anything Seabourne offers.

"We ship into several European countries and each one needs the order presented differently."

Destination is resolved before the order reaches the warehouse. Supply Lens applies the right delivery service, address format and any documentation reference per country, so cross-border orders arrive ready to ship rather than being held while somebody works out what is missing.

We have different carrier rules for DTC and B2B orders but Seabourne can't tell them apart.

The originating channel is passed with every order as a custom field. DTC orders from Shopify and B2B orders from your ERP arrive in Seabourne with a channel identifier attached. Your channel-specific carrier rules then apply correctly: DTC gets the consumer parcel carrier, B2B gets the business carrier. The distinction that Seabourne needs to route correctly is present in the order data from the moment it arrives.

Stock levelss from Seabourne never make it back to our ERP, so our margin reporting is always off.

When Seabourne creates a shipment, it records the actual carrier charge. Supply Lens captures that cost and returns it to your ERP against the relevant sales order or despatch record. Your margin calculation for that order now reflects what you actually paid for shipping, not an estimate and not a manual entry. Finance reporting and per-order profitability analysis both benefit without any additional work.

We ship from multiple sources (Shopify DTC, our ERP for B2B and two marketplaces) and Seabourne only sees the Shopify ones.

Supply Lens connects all four sources to Seabourne simultaneously. Each connection applies the correct transformation for that source: Shopify orders formatted one way, ERP sales orders formatted another, marketplace orders handled with their own channel identifiers. Seabourne sees all your orders in one place, each with its channel identified, and every despatch confirmation routes back to the right source system.

Getting started

A complete Seabourne integration
in days.

The setup centres on your SKU cross-reference, how bundles are held and which stock figure each channel should publish. Once that is mapped, everything else follows.

What we need from you
Seabourne API credentials
API key and secret from your Seabourne account settings
Source system credentials
Shopify, Unleashed, Enterpryze or whichever systems are sending orders to Seabourne
Your Stock and SKU accuracy
A summary of the rules you have set up (what conditions they check and what fields they depend on) so we can ensure those fields are populated correctly in every order
Weight and dimension source
Where item weights and dimensions are stored (ERP product record, order field or a separate lookup) and how they should be passed to Seabourne
Channel identifiers
How different order sources should be identified in Seabourne custom fields, so channel-specific carrier rules apply correctly
Sample orders from each source
To validate that SKUs resolve, bundles explode correctly and stock updates apply as expected before go-live
How we get you live
1
Scope
Order sources, SKU cross-reference, bundle definitions and channel identifiers mapped out.
2
Configure
Each order source connected and data enrichment configured so all rule-driving fields are populated.
3
Test
Orders from each source sent through staging. Automation rules validated against real data. Shipments and costs returned and verified.
4
Go live
Production activated. All flows monitored from day one.

If you add new Stock and SKU accuracy that depend on additional order fields, Supply Lens can be updated to pass those fields without rebuilding the integration.

Ready to connect every order
source to Seabourne?

Orders from any source. Automation rules that fire correctly. Shipments and costs back automatically. 30-day trial available.