Eight record types, mapped for Acumatica
The objects most stores need, in Acumatica’s own terms. The mapping file lists every field before anything is built.
Sales orders
Store orders become Sales Orders through the contract-based endpoint.
PUT /entity/Default/{version}/SalesOrder
{ CustomerID, Details: [ ... ] }
GET /odata/StockByWarehouseCustomers
Matched or created with customer class, terms and addresses.
Stock and matrix items
Stock, non-stock and matrix items mapped to store products and variants.
Warehouse quantities
Available quantity per warehouse read through a generic inquiry.
Sales prices
Sales prices and price classes mapped to store prices and B2B tiers.
Invoices
AR invoices created per your release process.
Credit memos
Store returns become RMA orders and credit memos.
Shipments
Shipments with tracking numbers sent back to the store.
What Acumatica projects trip on
Every ERP has its own sharp edges. These are the ones we plan for from day one.
Endpoint versions
Contract-based endpoints are versioned, and an Acumatica upgrade can change which version you should use.
How we handle it: We pin the endpoint version and test it before every upgrade.
Custom fields
Fields added by customisation projects are not in the default endpoint.
How we handle it: We extend the endpoint so custom fields travel with the record.
API limits by licence
Your licence sets limits on API requests and concurrent connections.
How we handle it: We pace calls to your licence and measure headroom during the audit.
Fast reads
Reading stock record by record is slow on large catalogues.
How we handle it: We use generic inquiries over OData for bulk reads.
One web order, as Acumatica’s REST API sees it
A simplified version of what our integration sends to the contract-based endpoint for a single order. The numbers point to the choices that keep it reliable.
1"OrderType": { "value": "SO" },"CustomerID": { "value": "C000231" },2"CustomerOrder": { "value": "WEB-10482" },"Details": [3 { "InventoryID": { "value": "TR-RUN-12" }, "WarehouseID": { "value": "MAIN" }, "OrderQty": { "value": 2 } }],4"custom": { "Document": { "UsrChannel": { ... } } }- The endpoint version is pinnedThe URL names the contract version, here a 2024 R2 default endpoint. We pin it, so an Acumatica upgrade can’t change the shape of the data without warning.
- The store order number travels with the orderWe store it in the customer order field and search for it before creating anything, which makes retries safe.
- Lines resolve by inventory ID and warehouseEach store SKU maps to an Acumatica inventory ID, and matrix item variants map to their own IDs. The warehouse comes from the mapping, not a default.
- Custom fields ride alongFields from customisation projects go in the custom block, or we extend the endpoint so they appear as normal fields.
Stores, interfaces and tools we wire in

From audit to a running Acumatica sync
- Week 0
Audit call
Where Acumatica and the store disagree today.
Gap list - Weeks 1–2
Mapping
Endpoint version, items, warehouses and fields agreed.
Mapping file - Weeks 2–5
Build
Built against a test tenant, demoed weekly.
Test-tenant demo - Weeks 5–7
Parallel run
Old and new process side by side until totals match.
Signed-off recon - Week 8+
Run
Monitoring, daily reconciliation, monthly report.
Monthly report
What makes an Acumatica integration cost more, or less
The prices below are starting points. These are the things that move the quote after the audit.
Pushes the cost up
- Heavy customisation projectsEvery custom field, screen or workflow on sales orders needs mapping, an endpoint extension and tests.
- Matrix items with many attributesLarge matrix items with several attributes take careful variant mapping on both sides.
- Several tenants or branchesEach tenant or branch needs its own routing, credentials and reconciliation.
- Tight API limitsA licence with a low request allowance means more batching and generic-inquiry design up front.
Keeps it down
- A standard order flowIf Commerce Edition’s Shopify or BigCommerce connector covers you, you may not need us to build much at all.
- Clean inventory IDsStore SKUs that already match Acumatica inventory IDs save days of mapping.
- A test tenant ready on day oneA recent copy of production to build against keeps weeks two to five moving.
- A decision on who owns pricesAgreeing early whether Acumatica or the store owns each price avoids rework.
Acumatica sync budgets
Typical ranges. Your fixed quote follows the free audit; ERP licences and partner fees are separate.
Order sync
from $9,000Store orders into Acumatica, about 4 weeks
- Sales orders via REST
- Customer match or create
- Error path and alerts
Two-way sync
$14k–$20kOrders in; stock and prices out
- Orders, returns, shipments
- Warehouse quantities via GI
- Daily reconciliation
Managed
from $400/moSized to your syncs
- Five-minute failure alerts
- Upgrade re-testing included
- Monthly written report
About Acumatica integration
Anything else, ask on the audit call.
Ask an engineer
Not answered here? Ask on the free 30-minute audit call. An engineer replies within one business day.
Quick facts
- Based in Delhi, India Working across time zones, with written weekly updates.
- Fixed quote first Nothing is billed before you agree it.
- You own it The code, workflows and accounts are yours.
- Stores and ERPs Shopify, BigCommerce, WooCommerce and Adobe Commerce, with NetSuite, SAP Business One, Odoo and Dynamics 365.
Acumatica Commerce Edition has connectors. Why custom?
For Shopify or BigCommerce stores with a standard process, Commerce Edition’s connectors may be enough, and Intelligize Digital will say so. We build custom for other platforms, custom fields or rules the connectors cannot express.
What happens when we upgrade Acumatica?
Intelligize Digital pins the contract-based endpoint version and re-runs the sync tests against your upgraded test tenant before you switch.
Can you sync our custom fields?
Yes. We extend the endpoint so fields from your customisation projects travel with each record, and document the extension.
Will the sync use up our API limits?
Intelligize Digital paces calls to your licence limits, uses generic inquiries for bulk reads, and measures headroom during the audit.
Are you an Acumatica partner?
No. Intelligize Digital is an independent agency. We work alongside your Acumatica partner, who stays responsible for your licence and system.
How does the integration log in to Acumatica?
Through OAuth 2.0 with a connected application, or a session login for a dedicated integration user that is always logged out again so it does not hold an API session. Intelligize Digital uses a user with only the access rights the sync needs.
Can Acumatica tell us when stock changes?
Yes. Push notifications can send changes from a generic inquiry to a URL. Intelligize Digital uses them for timely stock updates and keeps a scheduled catch-up read so nothing is lost if a notification fails.
How do matrix items map to store variants?
Each store variant maps to the inventory ID of an Acumatica matrix item variant, with attributes such as size and colour recorded in the mapping file. Stock and order lines always use the variant inventory ID.
How do you avoid duplicate sales orders in Acumatica?
The store order number is saved on each sales order and the sync searches for it before creating one. A retried request then updates or skips the existing order instead of creating a second.
Acumatica integration terms, explained
The words you’ll see in our mapping file and hear from your Acumatica partner.
- Contract-based REST API
- Acumatica’s main REST API. Endpoints describe entities like SalesOrder and StockItem in a stable, versioned contract.
- Endpoint version
- The contract version in the URL, such as 24.200.001. Pinning it keeps integrations steady across upgrades.
- Endpoint extension
- An extended copy of a default endpoint that adds your custom fields or entities.
Read the detail: Acumatica integration terms, explained
- Generic inquiry
- A saved query built in Acumatica. Exposed over OData, it’s the fastest way to read stock for many items.
- Push notification
- Acumatica sending changes from a generic inquiry or query to a URL, so the sync hears about updates without polling.
- Matrix item
- A template item whose variants are generated from attributes like size and colour, each with its own inventory ID.
- Commerce Edition
- The Acumatica edition with built-in connectors for platforms including Shopify and BigCommerce.
- API limits
- Request and concurrency limits set by your licence. Every integration on the tenant shares them.
- Tenant
- A separate company database inside one Acumatica instance, each with its own data and users.
Other ERPs and platforms
What still gets typed
into Acumatica by hand?
Tell us your store, your Acumatica set-up and what gets re-keyed today. An engineer replies within one business day.
What happens next
- An engineer replies Within one business day, by email.
- A free 30-minute audit On a call with an engineer.
- A fixed quote It follows the audit. Nothing is billed before you agree it.