Connect a client who isn't on DigiOS, without asking them to change anything.
Your clients keep sending orders, notices and retailer documents the way they do today, in X12 or EDIFACT, over AS2, SFTP or a VAN, or by REST and webhooks. Client Link brings them in, and sends back receipts, shipment advices and inventory.
ERP and accounting
WorkingOrders and item lists in. Receipts and stock levels out.
RESTSFTP filesLast exchange 10:40Carriers
WorkingLabels and pickup bookings out. Tracking numbers back.
RESTWebhooksLast exchange 10:42Storefronts and marketplaces
WorkingOrders in. Shipment confirmations and stock levels out.
RESTWebhooksLast exchange 10:39Retailer EDI
Needs attentionPurchase orders and advance notices in. Shipment notices out.
X12 850, 856, 945EDIFACTAS2SFTPLast exchange 09:58The 09:58 purchase order (850) was turned back: ship-to code 4471 is not in your list of retailer stores.
Sam can actOpen the orderEquipment
WorkingScale weights and line signals in. Sort instructions out.
OPC UAMQTTModbus TCPEtherNet/IPLast exchange 10:42Client API
WorkingStock levels and order status out to each client's own system.
RESTWebhooksSAMLOIDCLast exchange 10:41Sample data
What it usually looks like
Every client sends a different spreadsheet.
A retailer's routing guide that lives in one person's head.
A document sent twice that opens two orders.
How it works
Share the layout.
Send us a client's order layout and a sample file. We send back a mapping sheet for you to approve.
Test it.
The client's sample runs through a test channel. Nothing reaches your floor yet.
Run it beside today.
The client's real orders arrive in DigiOS while your current process carries on. You compare the two.
Switch the client over.
Orders land on the floor. Receipts, shipment advices and inventory go back to the client.
What comes in and goes out
Moves by AS2, SFTP, a VAN or an EDI provider, or by REST and webhooks. Parties are identified by GLN where your partners use it.
| X12 set | Name | What it carries | Direction |
|---|---|---|---|
| 850 | Purchase Order | An order | In |
| 855 | Purchase Order Acknowledgment | What will ship | Out |
| 856 | Ship Notice/Manifest (ASN) | What shipped and how it is packed | In and out |
| 810 | Invoice | An invoice | Out |
| 940 | Warehouse Shipping Order | What to pick and ship | In |
| 943 | Warehouse Stock Transfer Shipment Advice | What is coming | In |
| 944 | Warehouse Stock Transfer Receipt Advice | What arrived | Out |
| 945 | Warehouse Shipping Advice | What shipped, and when | Out |
| 947 | Warehouse Inventory Adjustment Advice | A change to stock | Out |
| 846 | Inventory Inquiry/Advice | What is on hand | Out |
| 997 | Functional Acknowledgment | That a document arrived | In and out |
| 204 | Motor Carrier Load Tender | A load offered to a carrier | Out |
| 214 | Transportation Carrier Shipment Status Message | A carrier's status | In |
| 210 | Motor Carrier Freight Details and Invoice | A carrier's freight bill | In |
For partners who work in EDIFACT
| EDIFACT message | Name | Direction |
|---|---|---|
| ORDERS | Purchase order | In |
| DESADV | Despatch advice | Out |
| INVRPT | Inventory report | Out |
A bad document gets one place to go
A document that is rejected, late or missing goes to one queue with its reason, which you can read on screen and over the API. A document sent twice never opens a second order. When a client fixes its layout, you run the document through again.
What we need from you
The client's layout and a sample file for each document. A contact at the client for questions. That is all.
Questions
Does the client have to change anything?
No. They send what they send today.
Do we keep our current WMS?
Yes. Client Link works beside it.
What if the client is on DigiOS?
Then you connect directly.
Send us one client's order layout.
We'll send back a mapping sheet. You'll know what it takes before you commit to anything.