Skip to content
API key2 triggers3 actions

Countmill integration for Shopify

Countmill is a partner ERP: orders, customers, products and fulfillments are normalised into one envelope shape and sent to Countmill's ingest endpoint, and fulfillments and inventory levels it reports back are polled and written to the connected system.

ShopifyCountmill
  • Shopify
  • Countmill

2 triggers in, 3 actions out — each step a row in the run record.

Triggers and actions

What Countmill 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
  • Fulfillment ready to acknowledge

    fulfillment.pending

    Polling
  • Inventory level changed

    inventory.changed

    Polling

Actions

3
  • Ingest ERP record

    ingestEnvelope

  • Acknowledge fulfillment

    ackFulfillment

  • Apply compliance request

    applyCompliance

Setup

Connecting Countmill

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

  1. 1

    Add your Countmill credentials

    Paste the API key, base URL and channel connection ID Countmill gives you when you install the bundle from its side. They are sent as a bearer token on every call and stored encrypted.

  2. 2

    Bindato tests the connection

    Bindato calls Countmill's /ping endpoint with the channel key you were issued and refuses the connection if the id it returns does not match the channel it was minted for.

  3. 3

    Install a bundle or build a flow

    Pick a bundle that uses Countmill, 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 Countmill

What is a channel key, and why does it matter?
It is the credential Countmill mints for one specific connection — not a general account token. Bindato's connection test checks that the key's own connection id matches what you pasted, so a key from a different channel is rejected rather than silently connected to the wrong one.
Why are both Countmill triggers polling?
Countmill does not push events in its current version. Fulfillment ready to acknowledge and Inventory level changed are both fetched on a 15-minute schedule with a cursor, so nothing is read twice.
What does Acknowledge fulfillment do?
It writes the connected system's fulfillment id back to Countmill against the ERP fulfillment it matches, which is what stops that same fulfillment from being polled again.

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.