What moves, and when
Lesson 2 of 15 7 min read
The Enterpryze message types, which way each one flows, and how a typical order travels from storefront to Enterpryze and back.
Before you configure anything, you need a clear picture of which data you want to move and in which direction. In this lesson you will learn the Enterpryze message types, how to read "send" and "receive", and how the three core flows (orders, stock and despatches) fit together.
Send and receive are from Supply Lens's point of view
Every Configuration on an Integration has a direction: Send, Receive, or both. These are always from the perspective of Supply Lens, not Enterpryze:
- Send means Supply Lens sends the Document into Enterpryze. Creating a sales order in Enterpryze is a send.
- Receive means Supply Lens receives the Document from Enterpryze. Picking up stock levels from Enterpryze is a receive.
A quick way to remember
Stand in Supply Lens's shoes. If the data is leaving Supply Lens for Enterpryze, it is a send.
The message types
The help centre lists these message types for Enterpryze:
| Data | Direction |
|---|---|
| Business Partner (Customer) | Supply Lens ↔ Enterpryze |
| Credit | Supply Lens → Enterpryze |
| Inventory | Enterpryze → Supply Lens |
| Invoice | Enterpryze → Supply Lens |
| Order (Sales Order) | Supply Lens ↔ Enterpryze |
| Product (Item Master) | Enterpryze → Supply Lens |
| Purchase Order | Supply Lens → Enterpryze |
| Shipment (Despatch) | Enterpryze → Supply Lens |
| Warehouse Order | Supply Lens → Enterpryze |
The configuration settings for several of these cover more than one direction. The Invoice settings include options for creating invoices and payments in Enterpryze as well as for picking invoices up from it, and the Shipment settings include linking a delivery created in Enterpryze back to its sales order. You will meet these in the settings deep dive. Agree the direction of each message type with your implementer when you plan the project.
The three core flows
Most Enterpryze projects start with three flows: orders in, stock out, and despatches back.
Orders in
Two decisions shape this flow, and they get a module of their own: which Business Partner each order is assigned to, and how each line's SKU is matched to the Enterpryze Item Master.
Stock out
Supply Lens receives inventory from Enterpryze and passes it to the storefront through a Mapping. You can limit which Enterpryze warehouses count.
Despatches back
Where Mappings come in
A Configuration says what the Enterpryze Integration can send or receive. A Mapping says where each Document goes next: for example, "Orders from WooCommerce go to Enterpryze" or "Inventory from Enterpryze goes to WooCommerce". You need both. A Configuration with no Mapping moves nothing anywhere useful.
Fernhill plans its flows
Fernhill writes its plan on one page before touching Supply Lens:
- Order, send: WooCommerce orders become Enterpryze sales orders.
- Inventory, receive: Enterpryze stock goes to WooCommerce, from the main warehouse only.
- Shipment, receive: despatches go back to WooCommerce so customers get their tracking email.
Invoices and purchase orders can wait for a later phase. Keeping phase one small makes testing faster.
Recap
- Send means into Enterpryze, receive means out of Enterpryze, always from Supply Lens's point of view.
- Enterpryze message types cover Business Partners, orders, invoices, credits, inventory, products, purchase orders, shipments and warehouse orders.
- The core flows are orders in, stock out and despatches back.
- Configurations say what the Integration handles. Mappings say where each Document goes.
- Agree the direction of each message type before you configure it.
Quick guides for this topic
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.