Worked example: Hilltop connects its 3PL
Lesson 7 of 21 7 min read
Follow Hilltop from an empty Integration to a configured, tested connection to its 3PL, pulling together everything in this module.
You've seen each step on its own. This lesson puts them together in order, using Hilltop's connection to Brookside Fulfilment, so you can see how the decisions link up, including the master data the Integration relies on.
The starting point
- Already live: Shopify and Unleashed, with Orders and Inventory Mappings.
- Master data ready (from the previous course): the Brookside Fulfilment Party, the Brookside Warehouse Location with its Unleashed and Mintsoft codes, and Products with Brookside Warehouse as their default fulfilment Location.
- Credentials: Brookside has sent the connection details for Hilltop's account on their Mintsoft system.
Step by step
- Create. In Settings → Integration setup → Integrations, Priya clicks + ADD INTEGRATION, searches "Mintsoft", clicks ADD, enters the details from Brookside and clicks CONNECT.
- Rename. She clicks the pencil and names it Brookside (Mintsoft), so no one confuses it with a future second warehouse.
- Leave it disabled. Activation stays on Disabled while she sets it up, so nothing moves before she's ready.
- Configurations. She adds Warehouse Order (Send) and Shipment (Receive), creating the default JSON for each.
- Check the other end. On Unleashed she confirms Warehouse Order (Receive) and Shipment (Send) Configurations exist, and on Shopify that Shipment (Send) exists for tracking.
- Defaults. She leaves State unset (not EDI) and Default Unit of Measure unset, because Brookside handles both bags and cases and the Product defaults already cover that.
- Master data check. She opens the Brookside Warehouse Location and confirms its Mintsoft Warehouse Id is scoped to the new Integration. She also checks whether Brookside expects a client code on its messages; if so, it belongs on a Party as a Mintsoft Client ID identifier.
- Mappings and schedule. These come next, in Modules 3 and 5.
What the setup looks like now
Dotted arrows are flows that are configured on both Integrations but not yet routed or switched on.
Why this order?
| Decision | Reason |
|---|---|
| Keep it disabled until the end | A half-configured Integration that's enabled can start receiving or sending before Mappings and master data are ready. |
| Configure both ends of each flow | A Send Configuration with no matching Receive on the other Integration means a flow that can never complete. |
| Check master data before go-live | The Integration can connect perfectly and still fail every Document if a warehouse code is missing. |
Shopify webhooks
For Shopify, the setup guide recommends enabling webhooks: expand the Shopify tile and click Setup in the Webhooks section. Webhooks let Shopify push new orders instantly instead of waiting for the next scheduled run. The next module explains how schedules and webhooks work together.
Recap
- Create the Integration, rename it clearly, and keep it disabled while you configure it.
- Add Configurations on both ends of every flow, with the right directions.
- Set State and Default Unit of Measure only when they apply.
- Confirm the master data the Integration relies on, such as warehouse and client codes.
- Mappings and schedules complete the setup; enable the Integration last.
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.