Connect Make and Shopify: log orders and notify the right team

Keep an order log separate from fulfilment approval

This example records the order ID, timestamp, total, currency and payment state, then sends an internal notification. Order creation is not proof of payment or permission to ship. Make documents a paid Shopify account requirement for this connection. Confirm the store and connection conditions available for practice before planning a live scenario or incurring a subscription.

Reuse an appropriate store connection

Select the intended store in the Shopify module and review its requested access. Inspect existing connections before creating another for the same app and store combination; overlapping connections can affect scopes. Logging orders does not inherently require changing inventory or creating fulfilments. Separate those write capabilities from this exercise and check who is allowed to authorize the integration.

Distinguish new orders from updates

Choose an available order trigger and limit its starting point to the practice records. A new-order workflow and a status-update workflow serve different purposes. Use the store plus order ID as the destination key: insert on the first arrival and update the relevant status on later arrivals. Adding a fresh spreadsheet row for every notification makes order counts unreliable.

Model orders and line items separately

A three-product order still has one order total. Store that total once in an order table. If item-level reporting is needed, use a separate table with order and line-item identifiers. Summing the order total after an iterator can multiply revenue by the number of items. Preserve the amount representation and currency together, and do not add different currencies without a defined conversion method.

Send only the information the team needs

Use an order reference, the state requiring attention and an authorized administration link in the internal message. Avoid copying addresses or phone numbers into a broad channel. Define which person checks unpaid, paid and cancelled orders. A message should request shipment only when the business's independent fulfilment conditions have been satisfied, not merely because an order trigger fired.

Recover updates without duplicating completed work

Repeat the same order delivery and expect no extra order row. Change its state and expect an update to the existing record. If storage succeeds and notification fails, use the stored order key and notification state to recover the latter. Relate cancellations or refunds to the original order rather than counting them as additional sales. Preserve enough state to explain the change later.

Reconcile counts, amounts and usage

Try one single-item order, one multiple-item order and an order with a changed state. Compare order counts, item counts and message counts separately. Match the reporting period and currency when reconciling against Shopify. Estimate Make searches, writes, line-item expansion and retries in addition to the store subscription. No measured usage or live order processing is claimed here; run these checks with authorized practice data before rollout.

• Estimate Shopify operating costs across orders, payments and apps
• Iterator and Aggregator in Make: arrays, bundles and summary outputs
• Prevent duplicate writes in Make with stable keys and recovery states