Where the reviewed products stand
Compare documented control across the named products and routes. Open a review for its plan, region and agreement (this is a selected sample).
0–10 on both axes · Higher and further right means more documented control
Exact scores & review links (8)
| Vendor | Data access & portability | Build & act |
|---|---|---|
| Acumatica ↗ | 7.7* | 4.6* |
| Cin7 Core ↗ | 7.1* | 6.2* |
| Unleashed ↗ | 8.3* | 5.8* |
| Shopify ↗ | 7.7* | 5.8* |
| Amazon Seller Central ↗ | 6.4* | 5.4* |
| Recharge ↗ | 6.1* | 4.3* |
| ShipStation ↗ | 4.7* | 5.6* |
| Permute ↗Publisher self-assessment | 8.0* | 7.1* |
Axes average three dimensions each: access, third-party access and exit horizontally; action, continuity and business logic vertically. Fixed 0–10 scale, midlines at 5 (overall grades use separate weights). * Some evidence is unresolved. Marker colors identify companies, not score bands. How to read the map ↗
Permute is included as a reference (it owns this site and is a publisher self-assessment). Its score is excluded from sample averages. Read the Permute review ↗
Compare the six dimensions
| Overall control | |
|---|---|
| Data access | |
| Third-party accessibility | |
| External action | |
| Continuity | |
| Data exit | |
| Business logic and customization | |
Product scopes, dates & reviews
Acumatica
ERP · Checked 2026-10-12
Acumatica / customer-instance contract REST API, custom fields and workflow actions. License-specific capacity is retained instead of assuming one hosted-plan quota.
Read findings and sources ↗Cin7 Core
Inventory management · Checked 2026-10-17
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.
Read findings and sources ↗| Customer control | Acumatica ↗ | Cin7 Core ↗ | Unleashed ↗ | Shopify ↗ | Amazon Seller Central ↗ | Recharge ↗ | ShipStation ↗ | Permute ↗ |
|---|---|---|---|---|---|---|---|---|
| Category | ERP | Inventory management | Inventory management | Ecommerce | Ecommerce | Billing | Shipping and fulfillment | Databases and data platforms |
| Overall control | ||||||||
| Data access | ||||||||
| Third-party accessibility | ||||||||
| External action | ||||||||
| Continuity | ||||||||
| Data exit | ||||||||
| Business logic and customization | ||||||||
| Assessment scope | Acumatica / customer-instance contract REST API, custom fields and workflow actions. License-specific capacity is retained instead of assuming one hosted-plan quota. | 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. | Unleashed product-catalog API reads/create-update, product change webhooks and product CSV exports for inventory workflows. Accounting, payroll, complete stock-ledger history and whole-ERP restore are excluded. | Shopify / one-merchant custom-distribution app using the GraphQL Admin API for ordinary authorized store operations. This grade excludes reusable public-app distribution and applications primarily transferring Merchant Data to third parties. | Amazon Selling Partner API / Professional seller private application, reports and listing operations. Public apps and restricted personal-data roles have additional reviews. | Recharge API 2021-11 / subscription records, updates and lifecycle webhooks; accepted partner OAuth and merchant-owned API tokens are distinct routes, separate from storefront tokens and payment vaults. | ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts. | Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. |
| Assessment checked | 2026-10-12 | 2026-10-17 | 2026-10-17 | 2026-10-17 | 2026-10-12 | 2026-10-16 | 2026-10-16 | 2026-10-12 |
| Read the findings | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ |
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
Connect the CPG stack without losing product and order history
Consumer packaged goods (CPG) brands need a usable record of products, inventory and sales across channels. This collection follows brand operations from inventory systems to DTC storefronts and fulfillment. Retailer sell-through, EDI deductions, lot genealogy and complete production recipes need their own access checks; their presence in a product does not prove their availability on its assessed API.
Inventory and order operations
Start with the declared ERP or inventory route. Check SKU identities, units of measure and stock by location before assuming two systems describe the same product or available quantity.
DTC and marketplace channels
Compare the records that can leave each sales channel, including line items, customer identifiers and refunds. Marketplace authorization and DTC store authorization can have different commercial and distribution conditions.
Subscriptions and fulfillment
Keep recurring-order records separate from shipment records. A portable copy needs the identifiers that connect a subscription, order, return and shipment; a successful API response alone does not establish that chain.
What to verify before connecting or migrating
- Can you export stable SKU, order-line and location identities with their original units?
- Which lot, expiry, returns and retailer-specific records are outside the assessed interface?
- Can a new system rebuild current inventory and open orders after the change history expires?
Industry references establish terminology and business context. The linked vendor reviews contain the assessed API, commercial and export evidence (with their own product scopes and check dates).
Consumer Brands Association: the CPG industry ↗ · Acumatica: Consumer Packaged Goods (CPG) ↗
Who can connect?
Yes No- Unknown
A check means the column applies to that route (customer credentials can still require provider approval). Report exports use the customer account without separate API credentials. Open a connection method for its authentication, requirements and last review date.
What each review covers
Acumatica ↗
Acumatica exposes contract REST interfaces and custom workflow actions. Integration capacity is licensed per instance and shown in customer monitoring screens.
Acumatica / customer-instance contract REST API, custom fields and workflow actions. License-specific capacity is retained instead of assuming one hosted-plan quota.
Cin7 Core ↗
Cin7 Core exposes paginated product records, availability and product mutations through its own V2 API. Production API connections require an Integration add-on; Cin7 Omni uses a different API and credentials.
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.
Unleashed ↗
Unleashed exposes an iterable product catalog, modified-since queries and named product create/update operations. Product webhooks include update and deletion identities; their bounded retries are distinct from a retained change log. Product CSV export offers a separate current-copy route.
Unleashed product-catalog API reads/create-update, product change webhooks and product CSV exports for inventory workflows. Accounting, payroll, complete stock-ledger history and whole-ERP restore are excluded.
Shopify ↗
A one-merchant custom app supports useful store access. Public connectors face a separate regime of app review, Shopify billing and revenue share; data-transfer and migration applications also face purpose restrictions.
Shopify / one-merchant custom-distribution app using the GraphQL Admin API for ordinary authorized store operations. This grade excludes reusable public-app distribution and applications primarily transferring Merchant Data to third parties.
Amazon Seller Central ↗
Private SP-API apps avoid public listing, but require a Professional seller account and approved roles. Historical fee announcements should not be treated as current charges.
Amazon Selling Partner API / Professional seller private application, reports and listing operations. Public apps and restricted personal-data roles have additional reviews.
Recharge ↗
Recharge exposes subscription updates and delete events through merchant tokens or approved partner OAuth. Failed webhook delivery can retry for 48 hours; missed history still needs current-state reconciliation.
Recharge API 2021-11 / subscription records, updates and lifecycle webhooks; accepted partner OAuth and merchant-owned API tokens are distinct routes, separate from storefront tokens and payment vaults.
ShipStation ↗
ShipStation V2 supports structured shipment records and create/update operations. Its list API caps pagination at 10,000 results, requiring narrower date/filter windows for larger collections.
ShipStation V2 platform shipment list/create/update with customer API keys; standalone ShipStation API formerly ShipEngine and deprecated V1 have separate billing/auth/sandbox contracts.
Permute ↗
Scoped APIs expose SQL reads, managed records and customer-authored operation code. Customer-built apps are supported, while complete workspace recovery, outbound CDC and minimum-plan access terms remain unresolved.
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.