Skip to content
API key2 triggers1 action

Cin7 integration for Shopify

Sales orders are created in Cin7 Core; stock movements and shipped orders are polled and written back to the store.

ShopifyCin7
  • Shopify
  • Cin7

2 triggers in, 1 action out — each step a row in the run record.

Triggers and actions

What Cin7 can do in a flow

Declared in the connector's code and validated when the engine boots. Each trigger names how it receives events.

Triggers

2
  • Stock changed

    stock.changed

    Polling
  • Order shipped

    order.shipped

    Polling

Actions

1
  • Create sales order

    createSalesOrder

Setup

Connecting Cin7

Three steps from the dashboard. The connection test is a real call, and its result is stored on the connection.

  1. 1

    Add your Cin7 credentials

    Paste the account id and application key from Cin7 Core. They are sent as a pair of request headers on every call and stored encrypted.

  2. 2

    Bindato tests the connection

    Bindato calls the account endpoint and records the company name it returns.

  3. 3

    Install a bundle or build a flow

    Pick a bundle that uses Cin7, connect the other system, and confirm its settings tab where it ships one. Or start a flow from one of the triggers listed above.

Questions

About Cin7

Why are the Cin7 triggers polling?
Both stock changes and shipped orders are polled every 15 minutes with a cursor. Stock is observed one way — Cin7 to Shopify — following Cin7's own recommendation; there is deliberately no Shopify-to-Cin7 stock push.
What does the stock trigger include?
SKU, product id, previous and current on-hand, and available quantity — enough to update a Shopify inventory level once the SKU is resolved to an inventory item.
Is there a Shopify + Cin7 bundle?
The connector is built and its bundle is listed as coming soon; its flow templates are not yet published.

See one order flow end to end.

Thirty minutes with a Shopify store you control. We connect it, install a bundle, and walk the run record together.