OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
V2 Product and Product Availability expose structured inventory records rather than complete ERP data.
Cin7 Core published V2 machine-readable reference ↗
Product resource group: Product GET and Product Availability GET · Checked 2026-10-17
Bulk delivery 8.8/10
Batched or iterable API requests
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
Product supports page traversal with Total; Product Availability has its own Page/Limit contract. Preserve IncludeDeprecated and requested optional expansions.
Cin7 Core published V2 machine-readable reference ↗
Introduction: Pagination; Product GET parameters; Product Availability GET · Checked 2026-10-17
Query expressiveness 8.8/10
Documented structured API filters
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
Product filters include name, SKU and ModifiedSince; availability has location, batch and category selectors.
Cin7 Core published V2 machine-readable reference ↗
Product GET and Product Availability GET parameters · Checked 2026-10-17
Access cost barrier 5.0/10
Higher plan, separately licensed add-on or fixed recurring access fee
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
A production Core API connection requires an Integration add-on. Flex API is an additional support-qualified option; the amount is unresolved.
Cin7 Core API Integration add-on and Flex API ↗
Requires integration add-on: Cin7 Core API; Flex API · Checked 2026-10-17
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
Customers create API applications to link different applications/add-ons; the provider supplies customer steps for third-party keys, without a separate approval step on this route.
Connecting to the Cin7 Core API ↗
Per-company Account ID; multiple API Applications · Checked 2026-10-17
Downstream permission -
-
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
Credential-based integration and export instructions do not establish complete contractual downstream-use or AI-use rights.
Connecting to the Cin7 Core API ↗
Connecting API applications; credentials must remain secret · Checked 2026-10-17
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
Product POST creates and PUT updates. PUT requires ID; SKU must be unique and Type is read-only on PUT.
Cin7 Core published V2 machine-readable reference ↗
Product resource: Available Fields for Product; POST and PUT request examples · Checked 2026-10-17
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
A customer can create multiple applications and connect different applications/add-ons with their own credentials, subject to the production Integration license.
Connecting to the Cin7 Core API ↗
API setup; multiple API Applications · Checked 2026-10-17
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
ModifiedSince returns changed product master records; stock availability is a separate current-state collection.
Cin7 Core published V2 machine-readable reference ↗
Product GET: ModifiedSince; Product Availability GET · Checked 2026-10-17
Limit visibility 7.5/10
Numeric usage or polling guidance
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
V2 documents 60 calls per minute and a 429 response. A runtime remaining/reset budget was not established.
Cin7 Core Inventory API V2 reference ↗
API Status Codes: 429; Connecting to the API: per API Application limits · Checked 2026-10-17
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
ModifiedSince and IncludeDeprecated support changed and deprecated product records. Universal hard-delete identities are unverified.
Cin7 Core published V2 machine-readable reference ↗
Product GET parameters: ModifiedSince and IncludeDeprecated · Checked 2026-10-17
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
Overlapping ModifiedSince queries recover current product changes; fresh pagination rebuilds current records. Separately entitled webhooks have six attempts then deactivate, without verified retained event replay.
Cin7 Core published V2 machine-readable reference ↗
Product GET parameters; Webhooks delivery attempts and deactivation · Checked 2026-10-17
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
V2 JSON responses provide structured product and availability records outside the service.
Cin7 Core published V2 machine-readable reference ↗
Product GET response examples; Product Availability GET response · Checked 2026-10-17
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
Trial and subscription access documentation does not establish a defined customer cancellation retrieval window.
Connecting to the Cin7 Core API ↗
Account and trial requirements · Checked 2026-10-17
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
Portable product/availability records are established; optional BOM, movements and attachments require separate selection and verification. No native whole-product restore is established.
Cin7 Core published V2 machine-readable reference ↗
Product GET optional IncludeBOM, IncludeMovements and IncludeAttachments; availability response · Checked 2026-10-17
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 5.0/10
Customer-editable native workflows or agent configurations
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
The Automation add-on allows native events/actions/conditions and external notification templates.
Cin7 Core Automation module ↗
Automation module; Configuring Notifications; External delivery · Checked 2026-10-17
Rights to custom logic -
-
Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes.
The native automation guide does not establish ownership, reusable export or independent execution rights for definitions.
Cin7 Core Automation module ↗
Workflow automation and message templates · Checked 2026-10-17
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
A customer with Cin7 Core API Setup permission creates an API application. Each company has its own Account ID, and applications have separate keys and rate budgets. The provider documents connecting other applications through these credentials; a separate public listing is not assumed.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Product supports Page/Limit, name/SKU filters, ModifiedSince and IncludeDeprecated. Default page size is 100, maximum 1,000. Product Availability separately supports location, batch and category filters; enumerate both collections with their selection parameters intact.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer Cin7 Core V2 API application | API key | Customer | No | customer api setup permission generates per-company account id and per-application key; api-auth-accountid and api-auth-applicationkey headers. integration add-on required for production. cin7 omni basic authentication is not this route. | 2026-10-17 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
API connections require an Integration add-on; the provider lists API as an add-on across its Core tiers. Flex API is separately available through support, and the exact API access amounts remain unpublished in the reviewed sources. Trial API access does not establish included production access.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
POST /product creates and PUT /product updates a product. PUT requires its ID, SKU is unique, and Type is read-only on update. No universal mutation idempotency or optimistic concurrency contract was established.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Overlap ModifiedSince product queries and retain deprecated products explicitly. Availability has its own current-state traversal, so stock-level changes require reconciliation or separately entitled notifications. Webhooks require Automation, allow five subscriptions of the same type, attempt delivery six times and deactivate after exhaustion; this does not establish retained event replay.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. ModifiedSince and IncludeDeprecated support changed and deprecated product records. Universal hard-delete identities are unverified. | Cin7 Core published V2 machine-readable reference ↗Product GET parameters: ModifiedSince and IncludeDeprecatedChecked 2026-10-17 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. Overlapping ModifiedSince queries recover current product changes; fresh pagination rebuilds current records. Separately entitled webhooks have six attempts then deactivate, without verified retained event replay. | Cin7 Core published V2 machine-readable reference ↗Product GET parameters; Webhooks delivery attempts and deactivationChecked 2026-10-17 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Current product and stock records can leave as structured JSON. Optional BOM, movements and attachment fields must be requested explicitly; attachment metadata is not proof that every file payload was preserved. Fresh traversals rebuild current scoped records without restoring deleted data or all native configuration.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
The separately subscribed Automation module supports native events, conditions, actions and external notifications. Ownership and independent execution of native definitions remain unverified (client integrations are separate artifacts).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. V2 Product and Product Availability expose structured inventory records rather than complete ERP data. | Cin7 Core published V2 machine-readable reference ↗Product resource group: Product GET and Product Availability GETChecked 2026-10-17 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. Product supports page traversal with Total; Product Availability has its own Page/Limit contract. Preserve IncludeDeprecated and requested optional expansions. | Cin7 Core published V2 machine-readable reference ↗Introduction: Pagination; Product GET parameters; Product Availability GETChecked 2026-10-17 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. Product filters include name, SKU and ModifiedSince; availability has location, batch and category selectors. | Cin7 Core published V2 machine-readable reference ↗Product GET and Product Availability GET parametersChecked 2026-10-17 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. Customers create API applications to link different applications/add-ons; the provider supplies customer steps for third-party keys, without a separate approval step on this route. | Connecting to the Cin7 Core API ↗Per-company Account ID; multiple API ApplicationsChecked 2026-10-17 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | Higher plan, separately licensed add-on or fixed recurring access feeCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. A production Core API connection requires an Integration add-on. Flex API is an additional support-qualified option; the amount is unresolved. | Cin7 Core API Integration add-on and Flex API ↗Requires integration add-on: Cin7 Core API; Flex APIChecked 2026-10-17 |
| What permission is needed for the documented downstream use? | -Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. Credential-based integration and export instructions do not establish complete contractual downstream-use or AI-use rights. | Connecting to the Cin7 Core API ↗Connecting API applications; credentials must remain secretChecked 2026-10-17 |
| Which external write operations are documented? | Create and update in one business domainCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. Product POST creates and PUT updates. PUT requires ID; SKU must be unique and Type is read-only on PUT. | Cin7 Core published V2 machine-readable reference ↗Product resource: Available Fields for Product; POST and PUT request examplesChecked 2026-10-17 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. A customer can create multiple applications and connect different applications/add-ons with their own credentials, subject to the production Integration license. | Connecting to the Cin7 Core API ↗API setup; multiple API ApplicationsChecked 2026-10-17 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. ModifiedSince returns changed product master records; stock availability is a separate current-state collection. | Cin7 Core published V2 machine-readable reference ↗Product GET: ModifiedSince; Product Availability GETChecked 2026-10-17 |
| How are integration limits disclosed? | Numeric usage or polling guidanceCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. V2 documents 60 calls per minute and a 429 response. A runtime remaining/reset budget was not established. | Cin7 Core Inventory API V2 reference ↗API Status Codes: 429; Connecting to the API: per API Application limitsChecked 2026-10-17 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. V2 JSON responses provide structured product and availability records outside the service. | Cin7 Core published V2 machine-readable reference ↗Product GET response examples; Product Availability GET responseChecked 2026-10-17 |
| What retrieval rights are documented at cancellation? | -Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. Trial and subscription access documentation does not establish a defined customer cancellation retrieval window. | Connecting to the Cin7 Core API ↗Account and trial requirementsChecked 2026-10-17 |
| How can customers define their own business logic? | Customer-editable native workflows or agent configurationsCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. The Automation add-on allows native events/actions/conditions and external notification templates. | Cin7 Core Automation module ↗Automation module; Configuring Notifications; External deliveryChecked 2026-10-17 |
| What rights or portability are documented for custom workflow artifacts? | -Cin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. The native automation guide does not establish ownership, reusable export or independent execution rights for definitions. | Cin7 Core Automation module ↗Workflow automation and message templatesChecked 2026-10-17 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedCin7 Core Inventory API V2 / product master records and product availability, with Product create/update. Cin7 Omni, legacy Core V1, full accounting/ERP extraction and native system restore are separate scopes. Portable product/availability records are established; optional BOM, movements and attachments require separate selection and verification. No native whole-product restore is established. | Cin7 Core published V2 machine-readable reference ↗Product GET optional IncludeBOM, IncludeMovements and IncludeAttachments; availability responseChecked 2026-10-17 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Exact API Integration add-on and Flex API amounts
- Downstream contract, AI-use and redistribution rights
- Universal product hard-deletion events and retained webhook history
- Native workflow artifact ownership and independent execution
- Customer retrieval rights after cancellation
Documentation
Assessment checked 2026-10-17. Each answer retains its source and applicable route; the check date does not establish live account behavior.