Cin7 Core

Log into Cin7 Core Inventory, then open Integrations -> API. Create a dedicated API application for ShopMCP and copy both values:

• Account ID — unique to the Cin7 Core company.
• API Application Key — the secret key for this application.

Open Settings -> Integrations and click Connect on the Cin7 Core card. Paste the Account ID and API Application Key. ShopMCP verifies them against the company profile and stores the credentials encrypted at rest. When several companies are connected, select the exact company before running a workflow.

• Buying and receiving: investigate shortages, prepare purchase documents and review counted receipts or put-away.
• Warehouse and dispatch: review transfers, stock counts and fulfilment exceptions; prepare supported pick, pack, ship or tracking changes from staff evidence.
• Sales, support and catalog: prepare quotes, eligible customer/address corrections, return dispositions, product and pricing changes.
• Finance: reconcile invoice, credit, payment and journal records using an accountant-approved basis.
• Production, CRM and administration: review supported production stages, relationship records, reference data and integration configuration.

Find the Cin7 operator playbooks in the playbook library. Each review returns evidence, a proposal or manual handoff, a responsible operator and the next readback. Scheduled reviews prepare proposals only.

Ask ShopMCP to discover the actions currently available for your connection. For a supported action, it prepares a preview showing the selected company, exact records, before/after values, quantities and amounts, resulting stage and downstream effects. Open the returned approval link and review the complete proposal in your authenticated ShopMCP session.

• Credentials and an enabled-write setting do not approve an action. Your workspace, connection, API key and team write permissions must also allow it.
• Draft creation, document authorisation, physical receipt, dispatch and financial posting are separate decisions. Staff must supply actual movement or settlement evidence.
• After execution, ShopMCP checks the exact record against the approved change and returns the verification state. An uncertain response or mismatch requires reconciliation before retrying.
• Changed or expired proposals require a fresh preview and approval. Scheduled runs never approve or execute changes.

Unsupported or unverifiable actions return an explicit handoff with the missing capability, evidence, operator and next verification. Native user/role settings, RMA/warranty, carrier-label purchase, gateway money movement and supplier/customer email delivery need their own supported interface or connector. A Cin7 shipment or payment record does not prove carrier handover or bank settlement.

• 403 Forbidden — confirm that the Account ID and Application Key belong to the selected company and have not been revoked.
• 429 Too Many Requests — the API application has reached its rate budget. Wait for it to reset or reduce read volume; do not blindly retry a mutation.
• Action unavailable — inspect the reported workspace, connection, team permission, entitlement or readback requirement.
• Readback pending or unknown outcome — inspect and reconcile the existing plan. Preserve its record IDs and receipt; do not create a replacement action until the outcome is resolved.
• Unexpected empty pages — pagination support differs by endpoint. Disclose incomplete evidence before proposing an action.