NetSuite to Acumatica Migration Guide 2026: Why Companies Switch and How to Migrate Successfully
NetSuite to Acumatica Migration Guide 2026: Why Companies Switch and How to Migrate Successfully
Moving from Oracle NetSuite to Acumatica is not a normal software upgrade. It is an ERP-to-ERP transformation.
A business making this move is rarely starting with a clean accounting database. A mature NetSuite environment may contain years of financial history, several subsidiaries, multiple currencies, warehouses, open orders, inventory, custom records, custom segments, SuiteScript applications, saved searches, workflows, dashboards, SuiteApps, eCommerce integrations, EDI connections, payment platforms, warehouse systems, shipping tools, CRM applications, tax engines, and business rules that have evolved over many years.
That is why a NetSuite to Acumatica migration must be approached as a complete business transformation rather than a file conversion.
Companies researching Acumatica vs NetSuite usually begin by comparing functionality, usability, integrations, implementation, licensing philosophy, customization, reporting, industry fit, partner ecosystems, and long-term ERP cost.
But once a company decides that its current ERP is no longer the right fit, the question changes.
How do we leave NetSuite without losing the data, integrations, controls, reporting, and business processes our company depends on?
That is the purpose of this guide.
Acumatica has an established migration path for organizations moving away from NetSuite, and multiple businesses have publicly documented successful transitions from NetSuite to Acumatica.
Those migrations demonstrate an important point: companies do not usually replace ERP simply because another platform has a longer feature list. They replace ERP because the relationship between business value, cost, complexity, usability, integrations, support, customization, and future growth has changed.
A successful NetSuite migration to Acumatica should therefore solve more than the immediate reason for leaving NetSuite. It should create a cleaner, more maintainable, more connected ERP environment for the next stage of the company’s growth.
As an Acumatica Gold Partner, BizTech helps businesses plan, implement, customize, integrate, test, migrate, train, and support Acumatica environments.
BizTech also develops proprietary Acumatica connectors and enhancements for eCommerce, marketplaces, payments, warehouses, fulfillment, shipping, CRM, EDI, inventory processing, and specialized business workflows.
That combination is especially relevant for companies leaving NetSuite because a mature NetSuite environment is rarely isolated.
The migration may involve:
- financial data and general ledger history;
- subsidiaries, departments, classes, locations, and reporting dimensions;
- customers, vendors, contacts, and addresses;
- inventory, assemblies, matrix items, prices, lots, and serial numbers;
- open sales orders, purchase orders, invoices, bills, credits, and payments;
- projects, fixed assets, budgets, and historical transactions;
- NetSuite custom fields and custom records;
- SuiteScript business logic;
- SuiteFlow workflows;
- saved searches, reports, and dashboards;
- SuiteApps and third-party applications;
- eCommerce and marketplace integrations;
- warehouse, shipping, EDI, CRM, payment, and tax integrations.
The goal is not to copy every NetSuite object into Acumatica.
The goal is to preserve what creates business value, eliminate unnecessary technical debt, and design a new ERP environment around Acumatica’s strengths.
Why Companies Consider Leaving NetSuite
NetSuite is a mature cloud ERP platform. A serious NetSuite replacement guide should acknowledge that directly.
Companies do not normally replace a mature ERP because it suddenly stops processing transactions. They replace it because the relationship between business value, cost, flexibility, usability, support, technical dependency, and future requirements no longer works for them.
Common reasons organizations begin researching a NetSuite alternative include:
- the commercial model no longer fits the company;
- the organization wants broader ERP access across more employees;
- customization and technical maintenance have become expensive;
- the business depends too heavily on specialized NetSuite developers;
- reporting requires too much custom work;
- integrations are difficult to maintain;
- industry-specific requirements are not being handled efficiently;
- the existing implementation accumulated significant technical debt;
- users find the ERP difficult to adopt;
- support or partner relationships are no longer delivering sufficient value;
- a contract renewal has triggered a broader ERP evaluation;
- the company wants a different licensing, deployment, integration, or support philosophy.
A migration project should not begin with the assumption that every problem was caused by NetSuite itself.
Some issues may be caused by poor original implementation, excessive customization, incorrect processes, outdated integrations, bad data, insufficient user training, or years of uncontrolled changes.
Before migrating, the company should document:
- why NetSuite is being replaced;
- which business problems must be solved;
- which NetSuite functionality must be preserved;
- which processes should be redesigned;
- which third-party applications should remain;
- which customizations should be retired;
- what measurable outcomes Acumatica must deliver.
Without this step, the company risks spending significant money to recreate the same problems inside a different ERP.
Acumatica vs NetSuite After Years of ERP Ownership
An ERP comparison looks different after a company has already lived with ERP for several years.
A first-time buyer may ask whether the system supports inventory, multiple entities, CRM, manufacturing, eCommerce, or project accounting.
An experienced ERP customer asks harder questions:
- How expensive is it to change processes?
- How difficult is it to add users?
- How much specialized development do we need?
- Can we understand our own integrations?
- Can managers create useful reports without development?
- What happens when transaction volume doubles?
- How difficult are upgrades?
- How responsive is the partner ecosystem?
- Can the ERP adapt as our business model changes?
This is where Acumatica often becomes attractive.
Acumatica is designed around:
- open architecture;
- APIs and webhooks;
- configurable workflows;
- low-code and no-code functionality;
- industry-specific editions;
- partner-led implementation;
- growth-friendly user access;
- modern browser-based ERP architecture.
A company migrating from NetSuite can use the project as an opportunity to redesign its ERP around those principles.
What Changes After Moving from NetSuite to Acumatica?
The objective should not be to make Acumatica look exactly like NetSuite. Acumatica has a different platform philosophy.
Unlimited User-Oriented Pricing Philosophy
Acumatica promotes unlimited user access with pricing tailored around applications and resource consumption.
That can change ERP adoption. Instead of designing access primarily around user-seat economics, a company can ask: Who should have direct access to live ERP data?
That may include:
- warehouse users;
- project managers;
- supervisors;
- sales representatives;
- customer service;
- purchasing;
- finance;
- executives;
- field teams.
Broader participation can improve data quality, process discipline, and visibility.
Open Architecture
Acumatica supports:
- REST APIs;
- webhooks;
- business events;
- import and export scenarios;
- configurable workflows;
- customization projects;
- developer extensions.
For integration-heavy organizations, this provides an opportunity to redesign the technology stack around clearer and more maintainable interfaces.
Industry Editions
Acumatica provides industry functionality for:
- distribution;
- manufacturing;
- construction;
- retail and commerce;
- professional services;
- field service;
- project-based organizations.
A migration can therefore be designed around industry workflows instead of building every operational requirement through custom ERP code.
Partner-Led Delivery
Acumatica operates through its partner ecosystem.
The selection of an Acumatica implementation partner therefore becomes central to project success.
The partner normally plays a major role in discovery, configuration, migration, integration, customization, training, and support.
Real Companies That Replaced NetSuite with Acumatica
Published Acumatica customer stories demonstrate that NetSuite-to-Acumatica migration is already a real ERP scenario.
These results belong to specific companies and should not be treated as universal guarantees. They are useful because they show different migration patterns.
Quantum Group: Seven Companies on One Acumatica Platform
Quantum Group is a manufacturing and distribution company that replaced NetSuite with Acumatica Manufacturing Edition.
The business needed to manage financials across seven companies in three physical locations, support multiple users, improve reporting, and reduce problems associated with its previous ERP environment.
The published case study reports:
- seven companies managed on one platform;
- IT cost savings;
- a 30-day migration and implementation for that particular project;
- the ability to add users without additional user license fees.
The important lesson is not that every NetSuite migration takes 30 days.
The case demonstrates that a well-scoped multi-company migration can move to Acumatica without reproducing the commercial and operational model of the old ERP.
NuvoH2O: Omnichannel Operations and Lower Software Costs
NuvoH2O replaced a heavily customized NetSuite environment with Acumatica Distribution Edition.
The published case study reports:
- a 69% reduction in software costs during the first year;
- a 67% faster month-end close, from 15 days to 5 days;
- doubling of business and transaction volume;
- integration with BigCommerce, Amazon, and SPS Commerce;
- implementation in approximately six months for that project.
This case is particularly relevant for distribution and eCommerce companies because the target ERP was designed around inventory, warehouse management, real-time reporting, and open integrations.
cbdMD: NetSuite Replacement in High-Volume Manufacturing
cbdMD moved from NetSuite to Acumatica Manufacturing Edition.
The published case study reports:
- approximately $200,000 in annual software licensing savings;
- 30% faster order fulfillment;
- significantly higher shipment capacity;
- improved inventory cycle counting;
- integration with Shopify and quality-management software.
The architectural lesson is important: the company did not only migrate accounting.
Acumatica became a platform for manufacturing, distribution, warehouse management, CRM, compliance workflows, and integrations.
Shoebacca: Reducing IT Dependency
Online retailer Shoebacca replaced NetSuite and a homegrown warehouse system with Acumatica.
The published case study reports lower IT staffing requirements, concurrent ERP access for more than 40 employees, multiple entities managed on one platform, and greater integration flexibility.
What Can Be Migrated from NetSuite to Acumatica?
Most business-critical NetSuite data can be migrated, but there is rarely a perfect one-to-one object match.
The migration should be organized by business meaning rather than source table alone.
Organization and Financial Structure
- subsidiaries;
- locations;
- departments;
- classes;
- custom segments;
- chart of accounts;
- currencies;
- accounting periods;
- tax settings;
- intercompany relationships;
- consolidation structures.
Customer Data
- customers;
- contacts;
- billing addresses;
- shipping addresses;
- terms;
- credit limits;
- tax registrations;
- sales representatives;
- price levels;
- custom fields;
- customer hierarchy;
- external IDs.
Vendor Data
- vendors;
- contacts;
- addresses;
- payment terms;
- tax identifiers;
- currencies;
- payment information;
- custom fields;
- external IDs.
Inventory and Product Data
- inventory items;
- non-inventory items;
- service items;
- assemblies;
- kits;
- matrix items;
- variants;
- units of measure;
- prices;
- vendors;
- warehouse relationships;
- lot and serial information;
- inventory quantities;
- cost information;
- reorder parameters;
- attributes and custom fields.
Open Transactions
- sales orders;
- purchase orders;
- customer invoices;
- vendor bills;
- credit memos;
- payments;
- deposits;
- returns;
- transfer orders;
- open projects;
- other active operational documents.
Historical Transactions
Depending on the selected strategy:
- general ledger history;
- sales history;
- purchasing history;
- inventory transactions;
- payment history;
- project history;
- fixed asset history;
- bank activity;
- attachments and documents.
Customization Metadata
The migration should also inventory:
- custom fields;
- custom record types;
- custom forms;
- custom segments;
- saved searches;
- workflows;
- SuiteScripts;
- SuiteApps;
- custom reports;
- dashboard configurations.
These customization objects are not normally imported into Acumatica unchanged.
Their business purpose must be assessed and rebuilt using the appropriate Acumatica functionality.
How NetSuite Data Is Extracted for Migration
One of the most technical parts of a NetSuite data migration is extraction.
NetSuite provides several mechanisms for retrieving data.
Full CSV Export
NetSuite includes a Full CSV Export capability.
However, Full CSV Export does not necessarily provide every category of information required to reconstruct a complete ERP environment.
A serious migration should therefore not assume that one export function will create a complete dataset that can simply be imported into Acumatica.
Saved Search Exports
Saved searches are often among the most useful migration tools because the extraction team can define:
- record type;
- criteria;
- results;
- joins;
- internal IDs;
- external IDs;
- filters;
- custom fields.
Saved search results can be exported as CSV files.
Migration-specific searches can be created for customers, vendors, items, locations, transactions, open balances, custom records, and integration cross-references.
Report Exports
NetSuite financial and operational reports can be exported and used as reconciliation control sources.
This is particularly important when validating Acumatica balances after migration.
SuiteAnalytics Connect
For larger datasets, SuiteAnalytics Connect may provide structured access to NetSuite data for repeatable extraction and transformation pipelines.
SuiteTalk Web Services
Web services can be used to query NetSuite records programmatically where structured extraction is required.
SuiteScript-Based Extraction
For specialized environments, SuiteScript may be used to extract information that is not conveniently available through standard exports.
File Cabinet and Attachments
Documents and files require a separate migration or archival strategy.
The company should decide which documents should move to Acumatica, which should remain archived, how files should be linked to migrated records, and which content is subject to retention requirements.
NetSuite Saved Search Migration
Saved searches deserve special attention because many organizations effectively use them as operational applications.
They may control:
- work queues;
- warehouse exceptions;
- customer service processes;
- integration exports;
- management reports;
- collections;
- inventory decisions;
- approval reviews.
For each important saved search, document:
- business owner;
- record type;
- criteria;
- columns;
- formula fields;
- joins;
- scheduled delivery;
- dashboard usage;
- integration dependencies.
A NetSuite saved search may become:
- an Acumatica Generic Inquiry;
- a dashboard widget;
- a financial report;
- a standard report;
- a business event;
- a workflow condition;
- an integration endpoint;
- a Power BI dataset;
- something that is no longer required.
The correct target is determined by business purpose.
NetSuite-to-Acumatica Data Mapping
Extraction produces source data. Mapping determines how that data behaves in Acumatica.
A mapping specification should identify the source object, source field, source identifier, target object, target field, transformation rule, default values, validation, error handling, and reconciliation method.
| NetSuite Concept | Possible Acumatica Target | Design Consideration |
|---|---|---|
| Subsidiary | Company / Branch | Legal entity, currency, tax, reporting, and intercompany structure |
| Location | Branch / Warehouse / Warehouse Location | NetSuite locations may represent several different business concepts |
| Department / Class | Subaccount Segment / Reporting Dimension | Reporting should be redesigned instead of blindly copying source dimensions |
| Customer | Customer | Classes, terms, contacts, addresses, taxes, and external IDs |
| Vendor | Vendor | Terms, currencies, payments, taxes, and contacts |
| Inventory Item | Stock Item | Item classes, UOM, costing, warehouses, lot and serial rules |
| Saved Search | Generic Inquiry / Report / Dashboard / BI | Rebuild according to purpose rather than screen-for-screen |
| SuiteScript | Standard Functionality / Workflow / API / Customization | Preserve business logic rather than source code |
NetSuite Subsidiaries to Acumatica Companies and Branches
Multi-entity migration is one of the most important architectural areas.
A NetSuite OneWorld environment may contain subsidiaries with different base currencies, tax registrations, accounting structures, locations, intercompany relationships, user permissions, and reporting requirements.
Legal Entity Boundaries
The project must determine which subsidiaries represent actual legal entities and which exist primarily for operational or reporting purposes.
Branch Design
A source location may become:
- an Acumatica branch;
- a warehouse;
- a warehouse location;
- a reporting dimension;
- an archived concept.
Intercompany Transactions
The migration must identify:
- due-to and due-from accounts;
- intercompany customers and vendors;
- eliminations;
- cross-entity inventory movement;
- shared services;
- consolidation requirements.
Currency
The design should address base currencies, transaction currencies, exchange rates, historical rates, revaluation, and consolidation.
NetSuite Financial Data Migration to Acumatica
Financial migration is the foundation of the ERP replacement.
The company must be able to prove that Acumatica agrees with the approved NetSuite financial position at cutover.
Chart of Accounts
Review:
- active accounts;
- inactive accounts;
- control accounts;
- bank accounts;
- retained earnings;
- intercompany accounts;
- segment-based reporting;
- duplicate or obsolete accounts.
The chart should not necessarily be copied one-for-one.
Acumatica subaccounts and reporting dimensions may provide a cleaner reporting structure.
Opening Balances
Opening balances may be loaded by account, subaccount, branch, currency, and other approved dimensions.
Historical General Ledger
The company should choose between full transaction history, summarized historical balances, selected comparative periods, or opening balances only.
Financial Reconciliation
At minimum compare:
- trial balance;
- balance sheet;
- income statement;
- cash;
- AR control accounts;
- AP control accounts;
- inventory accounts;
- fixed assets;
- intercompany balances;
- retained earnings.
NetSuite Customer and Vendor Migration
Master data migration should improve quality rather than simply preserve every source record.
Customers
- customer ID;
- company name;
- contacts;
- billing addresses;
- shipping addresses;
- terms;
- credit limits;
- tax settings;
- currency;
- salesperson;
- pricing;
- hierarchy;
- external IDs;
- marketplace identifiers;
- custom attributes.
Vendors
- vendor ID;
- name;
- contacts;
- addresses;
- terms;
- currency;
- tax identifiers;
- payment information;
- item relationships;
- custom attributes;
- external IDs.
Duplicate Management
Duplicates may exist because of subsidiaries, currencies, locations, integrations, historical imports, and separate sales or billing relationships.
They should not be merged automatically without business review.
NetSuite Inventory Migration to Acumatica
Inventory is one of the most complex areas of ERP migration.
A successful transition must align item master data, physical quantities, financial value, warehouse structure, open demand, open supply, and external channel availability.
Item Types
- inventory items;
- non-inventory items;
- service items;
- assemblies;
- kits;
- matrix parents;
- matrix children;
- lot-numbered items;
- serialized items.
Location Mapping
NetSuite locations may map to Acumatica branches, warehouses, warehouse locations, or reporting dimensions.
Opening Inventory
The migration may need:
- on-hand quantity;
- available quantity;
- allocated quantity;
- lot balances;
- serial numbers;
- warehouse locations;
- inventory status;
- cost layers where applicable.
Inventory Reconciliation
Compare:
- NetSuite inventory;
- WMS inventory;
- physical inventory;
- eCommerce availability;
- inventory valuation;
- general ledger inventory accounts.
Migrating Open AR, AP, Sales Orders, and Purchase Orders
Open documents are often more important than closed historical transactions because the business must continue processing them immediately after go-live.
Accounts Receivable
- open invoices;
- credit memos;
- unapplied payments;
- customer deposits;
- remaining balances;
- due dates;
- currency;
- payment applications.
Accounts Payable
- vendor bills;
- vendor credits;
- prepayments;
- unapplied payments;
- remaining balances;
- due dates;
- currency.
Sales Orders
- customer;
- items;
- ordered quantities;
- shipped quantities;
- warehouse;
- prices;
- discounts;
- taxes;
- shipping method;
- customer PO number;
- channel identifiers;
- fulfillment state.
Partially fulfilled orders require special attention.
Purchase Orders
- vendor;
- items;
- ordered quantity;
- received quantity;
- warehouse;
- cost;
- expected date;
- currency;
- related receipts and bills.
NetSuite Historical Data Migration
One of the biggest migration decisions is how much history belongs in Acumatica.
There are several valid strategies.
Full Transaction-Level History
Advantages:
- users research history in one ERP;
- comparative reporting is easier;
- less dependency on the legacy account;
- customer and vendor history remains directly accessible.
Disadvantages:
- higher cost;
- longer testing;
- more data transformation;
- more reconciliation;
- higher risk of importing obsolete structures.
Limited Detailed History
The company migrates a selected time range such as the current fiscal year plus comparative periods.
Summary History
Detailed transactions stay archived while Acumatica receives summarized historical balances.
Opening Balances and Open Documents Only
Acumatica begins cleanly at cutover while legacy information remains accessible through controlled archival methods.
How to Choose
Consider:
- audit requirements;
- tax retention;
- customer service;
- warranty requirements;
- traceability;
- project history;
- comparative reporting;
- legacy system cost;
- migration budget;
- data quality.
NetSuite Custom Records Migration
NetSuite custom records may represent critical business processes, but a custom record should not automatically become a custom Acumatica object.
First identify why it exists.
A custom record may be:
- a genuine business entity;
- an extension of a standard record;
- an integration staging object;
- a reporting workaround;
- a process Acumatica already supports;
- an obsolete customization.
The migration process should:
- Inventory the custom record.
- Document fields and relationships.
- Identify scripts and workflows that use it.
- Identify saved searches and integrations that depend on it.
- Define the business requirement.
- Select the appropriate Acumatica design.
- Migrate data only after the target structure is approved.
NetSuite SuiteScript Migration to Acumatica
SuiteScript is NetSuite’s JavaScript-based customization framework.
A mature account may contain:
- user event scripts;
- client scripts;
- scheduled scripts;
- Map/Reduce scripts;
- RESTlets;
- Suitelets;
- workflow action scripts;
- mass update scripts;
- custom modules.
These scripts cannot simply be copied into Acumatica.
The platforms use different data models, APIs, events, security models, UI frameworks, and customization architectures.
A SuiteScript to Acumatica migration should classify each script by business purpose.
Document:
- what triggers it;
- which records it reads;
- which records it changes;
- which external systems it calls;
- how errors are handled;
- how frequently it runs;
- who depends on it;
- whether the requirement still exists.
A SuiteScript may be replaced by:
- standard Acumatica functionality;
- configuration;
- workflow automation;
- business events;
- import/export scenarios;
- REST APIs;
- webhooks;
- a scheduled integration service;
- a BizTech connector;
- custom Acumatica development.
Preserve business logic, not NetSuite source code.
NetSuite Workflow Migration
NetSuite workflows may control approvals, status changes, field updates, notifications, record creation, validation, routing, and business rules.
For each workflow, document:
- record type;
- trigger;
- states;
- transitions;
- conditions;
- actions;
- approvers;
- notifications;
- exceptions;
- integration dependencies.
Acumatica may support the requirement through standard workflow configuration, approval maps, business events, notifications, or custom logic.
The goal is to preserve the correct business control, not recreate SuiteFlow visually.
Migrating NetSuite Integrations to Acumatica
Integration architecture can be one of the largest components of a NetSuite replacement.
A mature environment may connect NetSuite with:
- Shopify;
- WooCommerce;
- Amazon;
- Magento;
- BigCommerce;
- Salesforce;
- payment gateways;
- banks;
- tax services;
- EDI providers;
- warehouse systems;
- shipping systems;
- 3PLs;
- planning software;
- BI tools;
- custom applications.
Create an integration inventory containing the system, owner, authentication method, entities, direction, frequency, volume, error handling, monitoring, NetSuite dependencies, and target Acumatica architecture.
Existing BizTech Acumatica Connectors
BizTech already develops solutions for many platforms commonly found around NetSuite.
- Amazon Connector;
- Shopify Connector;
- WooCommerce Connector;
- Magento Connector;
- PayPal Integration;
- ShipHero Connector;
- ShipStation Connector;
- DSCO;
- CommerceHub;
- EZCom;
- Salesforce;
- ServiceTitan;
- custom APIs;
- specialized warehouse, EDI, logistics, and CRM systems.
This can significantly reduce the amount of migration code that needs to be built from zero.
Do Not Rebuild NetSuite Inside Acumatica
This is one of the most important principles in the entire migration.
Users naturally ask for familiar behavior.
They may want the same screens, field names, approval steps, reports, scripts, and workarounds.
Some requirements should remain. Others exist only because the old ERP required them.
A stronger migration sequence is:
- Standard Acumatica functionality.
- Configuration and workflow.
- Existing BizTech or Acumatica ecosystem solution.
- Integration with a specialized external platform.
- Custom development only when genuinely required.
This approach can reduce implementation cost, technical debt, custom code, upgrade risk, support complexity, and training burden.
The purpose of leaving NetSuite should not be to build a NetSuite-shaped Acumatica. The purpose is to create a better ERP operating model.
NetSuite to Acumatica Migration Process
Phase 1: Migration Discovery
Review the business objectives, reasons for leaving NetSuite, modules, subsidiaries, locations, currencies, inventory, transactions, integrations, SuiteApps, custom records, SuiteScripts, workflows, saved searches, reports, users, and contract timing.
Phase 2: Acumatica Fit-Gap Analysis
Classify each requirement as:
- standard functionality;
- configuration;
- integration;
- existing BizTech product;
- custom development;
- process redesign;
- retirement.
Phase 3: Target Architecture
Design companies, branches, financial structures, warehouses, customers, vendors, security, workflows, integrations, reporting, historical data strategy, and deployment.
Phase 4: Extraction Design
Define the source and extraction method for every dataset.
Phase 5: Data Cleansing
Standardize, deduplicate, validate, and reconcile source data.
Phase 6: Acumatica Configuration
Configure the approved ERP applications and business structures.
Phase 7: Integrations and Customization
Develop only requirements approved through the fit-gap process.
Phase 8: Test Migration
Perform a realistic migration rehearsal using representative production data.
Phase 9: Financial and Operational Reconciliation
Compare Acumatica against approved NetSuite control reports and operational sources.
Phase 10: User Acceptance Testing
Users test complete business scenarios from beginning to end.
Phase 11: Training and Change Management
Train users by role and explain how the new Acumatica processes differ from the old NetSuite environment.
Phase 12: Final Cutover
Freeze NetSuite transactions, perform final extraction, migrate production data, reconcile balances, activate integrations, and approve production use.
Phase 13: Stabilization
Monitor users, integrations, reports, system performance, and exceptions after go-live.
NetSuite to Acumatica Migration Cost
There is no universal fixed migration cost.
Major cost drivers include:
- number of subsidiaries;
- number of locations;
- transaction volume;
- historical data;
- custom records;
- custom segments;
- SuiteScripts;
- workflows;
- saved searches;
- SuiteApps;
- integrations;
- industry requirements;
- data quality;
- reporting;
- training;
- cutover complexity.
| Cost Category | Examples |
|---|---|
| Acumatica Software | Applications, resources, storage, and deployment |
| Discovery | NetSuite audit, fit-gap analysis, architecture |
| Data Migration | Extraction, cleansing, mapping, imports, reconciliation |
| Customization Migration | Custom records, fields, SuiteScript, workflows |
| Integration Migration | Commerce, payments, WMS, CRM, EDI, tax, shipping |
| Reporting | Saved searches, reports, dashboards, BI |
| Testing and Training | Migration tests, UAT, user education |
| Go-Live and Support | Cutover, stabilization, monitoring, optimization |
What Reduces Migration Cost?
- clean data;
- limited historical scope;
- strong process owners;
- retiring obsolete scripts;
- using standard Acumatica workflows;
- using existing BizTech connectors;
- clear reporting requirements;
- fast decisions;
- phased implementation.
What Increases Migration Cost?
- many subsidiaries;
- complex intercompany processes;
- full detailed history;
- large custom-record footprint;
- extensive SuiteScript;
- hundreds of saved searches;
- many integrations;
- poor source data;
- compressed timeline;
- unclear scope.
NetSuite to Acumatica Migration Timeline
Migration duration can vary significantly.
Focused projects can be measured in weeks, while broader ERP transformations involving multiple entities, historical data, customizations, integrations, and complex operational processes may require several months.
Timeline is affected by:
- subsidiaries;
- data volume;
- history;
- modules;
- customization;
- integrations;
- user availability;
- testing;
- training;
- renewal timing.
The project should use milestones rather than relying on one unsupported universal duration.
When Should You Start Planning Before NetSuite Renewal?
Contract timing can materially affect migration risk.
12+ Months Before Renewal
Ideal for ERP research, Acumatica demonstrations, requirements workshops, contract review, customization inventory, integration inventory, and budget planning.
9–12 Months Before Renewal
Begin fit-gap analysis, data audit, target architecture, implementation partner selection, and detailed migration estimates.
6–9 Months Before Renewal
For many midmarket projects, implementation should already be active.
3–6 Months Before Renewal
A migration may still be achievable, but scope discipline becomes critical.
The company may need:
- phased rollout;
- temporary legacy access;
- limited historical migration;
- priority integrations;
- a transition period.
Less Than 3 Months
Do not force an unsafe cutover only to avoid renewal.
Assess whether a controlled migration is realistic or whether temporary overlap is safer.
NetSuite to Acumatica Migration for Manufacturing
Manufacturers may need to migrate:
- assemblies;
- BOMs;
- routing;
- work centers;
- production orders;
- MRP;
- WIP;
- labor;
- overhead;
- lot and serial tracking;
- quality integrations;
- manufacturing costing.
Manufacturing data usually requires more design than a direct record import.
NetSuite to Acumatica Migration for Distribution
Distribution projects may include:
- multi-warehouse inventory;
- sales orders;
- purchase orders;
- replenishment;
- customer pricing;
- returns;
- EDI;
- shipping;
- marketplaces;
- inventory analytics.
NetSuite to Acumatica Migration for eCommerce
Commerce migrations are highly integration-dependent.
The project may involve:
- Shopify;
- Amazon;
- WooCommerce;
- Magento;
- BigCommerce;
- payments;
- warehouses;
- shipping;
- returns;
- refunds;
- channel profitability.
BizTech’s connector portfolio can significantly reduce the amount of custom development required.
NetSuite to Acumatica Migration for Multi-Entity Companies
Multi-entity migration requires special attention to:
- subsidiaries;
- companies;
- branches;
- intercompany accounting;
- currencies;
- taxes;
- shared customers;
- shared vendors;
- security;
- consolidation;
- entity-specific integrations.
Common NetSuite-to-Acumatica Migration Risks
Risk 1: Treating CSV Export as a Complete Backup
Additional extraction methods may be required for a complete migration.
Risk 2: Rebuilding Custom Code Before Understanding It
SuiteScript should be analyzed by business purpose before development starts.
Risk 3: Missing Integration Dependencies
A saved search or custom field may be used by an integration even if end users do not recognize it as important.
Risk 4: Losing Cross-System IDs
External systems may store NetSuite internal IDs. Cross-reference planning is essential.
Risk 5: Migrating Too Much History
Historical migration can dominate cost and testing without providing equivalent business value.
Risk 6: Ignoring Attachments
Files may be operationally, legally, or financially important.
Risk 7: Rebuilding Every Saved Search
Many saved searches can be replaced with standard Acumatica inquiries, dashboards, reports, or alerts.
Risk 8: Underestimating User Acceptance Testing
Users must test complete processes rather than individual screens.
Risk 9: Rushing Cutover Around Renewal
Temporary overlap may be safer than an uncontrolled ERP launch.
Risk 10: No Post-Go-Live Monitoring
Real production volume often reveals exceptions that did not appear during testing.
Why Work with BizTech for NetSuite to Acumatica Migration?
BizTech is an Acumatica Gold Partner combining ERP implementation expertise with integration and custom product development.
This combination is particularly valuable during a NetSuite replacement.
A company may need:
- ERP discovery;
- data extraction;
- financial migration;
- inventory migration;
- customization analysis;
- integration redesign;
- Acumatica implementation;
- custom development;
- reporting;
- testing;
- training;
- cutover;
- support.
BizTech can coordinate these areas as one migration program.
Custom Acumatica Development
BizTech develops custom APIs, workflows, connectors, screens, business logic, and Acumatica enhancements.
Existing Connector Portfolio
BizTech solutions include:
- Amazon;
- Shopify;
- WooCommerce;
- Magento;
- ShipHero;
- ShipStation;
- DSCO;
- CommerceHub;
- EZCom;
- Salesforce;
- ServiceTitan;
- PayPal;
- Kit Processing;
- Consignment Processing;
- Gift Card Processing;
- custom integrations.
Ongoing Support
BizTech can provide integration monitoring, issue resolution, performance optimization, feature updates, customization maintenance, and ongoing Acumatica support.
Final NetSuite to Acumatica Migration Checklist
Business Case
- Reasons for replacing NetSuite are documented.
- Success metrics are defined.
- Executive sponsorship is confirmed.
- Contract dates are documented.
- Process owners are assigned.
NetSuite Inventory
- Modules are documented.
- Subsidiaries are documented.
- Locations are documented.
- Currencies are documented.
- Custom segments are documented.
- Custom records are inventoried.
- Custom fields are inventoried.
- SuiteScripts are inventoried.
- Workflows are inventoried.
- Saved searches are inventoried.
- SuiteApps are inventoried.
- Integrations are inventoried.
- Files and attachments are assessed.
Acumatica Target Design
- Companies and branches are approved.
- Chart of accounts is approved.
- Subaccounts are approved.
- Customer and vendor classes are approved.
- Item classes are approved.
- Warehouses are approved.
- Order types are approved.
- Security roles are approved.
- Workflow design is approved.
- Integration architecture is approved.
Data Migration
- Extraction methods are documented.
- Saved searches are tested.
- Data mapping is approved.
- Duplicates are resolved.
- Inactive records are reviewed.
- Historical strategy is approved.
- AR reconciles.
- AP reconciles.
- Inventory reconciles.
- Trial balance reconciles.
- Open documents are validated.
- Test migration is approved.
Integrations
- Every integration has an owner.
- Authentication is tested.
- Cross-references are defined.
- Error handling is tested.
- Retry logic is tested.
- Monitoring is enabled.
- Orders are tested.
- Inventory synchronization is tested.
- Payments are tested.
- Fulfillment is tested.
- Returns and refunds are tested.
Cutover
- NetSuite transaction freeze is scheduled.
- Final exports are scheduled.
- Backups and archives are available.
- Production migration is rehearsed.
- Reconciliation responsibilities are assigned.
- Go-live criteria are documented.
- Contingency plans are documented.
- Post-go-live support is scheduled.
Final Conclusion: Moving from NetSuite to Acumatica
Replacing NetSuite is a significant ERP decision.
The company may be moving away from an environment that has accumulated years of data, customizations, integrations, reports, and institutional knowledge.
That makes migration complex, but it also creates an opportunity.
A NetSuite replacement allows the business to ask questions that may not have been asked for years:
- Do we still need this customization?
- Should this saved search become a dashboard?
- Should this SuiteScript become a standard workflow?
- Do we need all historical data in the production ERP?
- Should this external application remain?
- Can our eCommerce integrations be simplified?
- Can more employees work directly in ERP?
- Can we reduce dependency on specialized development?
- Can reporting become more real-time?
- Can our ERP support the next stage of growth?
Acumatica provides a strong target platform for organizations that want modern cloud ERP, open architecture, industry-specific functionality, flexible integrations, customer-focused product direction, and growth-friendly user access.
But the platform alone does not determine migration success.
The project requires discovery, data extraction, mapping, financial reconciliation, integration architecture, customization redesign, testing, training, cutover management, and post-go-live support.
As an Acumatica Gold Partner, BizTech helps companies manage this complete transition.
NetSuite is the source. Acumatica is the new platform. BizTech helps build the migration path between them.
FAQ: NetSuite to Acumatica Migration
Can NetSuite data be migrated to Acumatica?
Yes. Financial data, customers, vendors, inventory, open transactions, subsidiaries, locations, projects, selected history, custom-field data, and many other records can be migrated. Exact scope depends on the NetSuite configuration and target Acumatica design.
How do you export NetSuite data for migration?
NetSuite supports several extraction methods including CSV exports, saved searches, reports, analytics connections, web services, and scripted extraction. Complex migrations often use several methods.
Can NetSuite saved searches be migrated to Acumatica?
Their business purpose can be migrated, but the saved search itself is not imported directly. It may be rebuilt as an Acumatica Generic Inquiry, report, dashboard, business event, workflow condition, integration endpoint, or BI dataset.
Can SuiteScript be migrated to Acumatica?
SuiteScript code cannot simply be copied because NetSuite and Acumatica use different APIs and customization frameworks. The business logic should be analyzed and reimplemented using standard Acumatica functionality, workflows, APIs, webhooks, integrations, or custom development.
Can NetSuite custom records be migrated?
Yes. The underlying data can often be migrated, but a target Acumatica data model must be designed first. Some custom records may become standard functionality, fields, attributes, custom tables, integrations, or may be retired.
How long does NetSuite to Acumatica migration take?
There is no universal duration. Project length depends on subsidiaries, data volume, customizations, integrations, historical requirements, testing, and scope. Focused migrations may be measured in weeks, while broader ERP transformations may require several months.
How much does NetSuite to Acumatica migration cost?
Cost depends on Acumatica applications, data volume, historical migration, subsidiaries, custom records, SuiteScripts, workflows, integrations, reporting, testing, training, and support. Structured discovery is required for a reliable estimate.
When should we begin planning before NetSuite renewal?
Begin as early as possible. Organizations with more time have more flexibility for discovery, data cleanup, integration development, testing, and controlled cutover.
Can several NetSuite subsidiaries be migrated to Acumatica?
Yes. Subsidiaries can be mapped to Acumatica companies and branches depending on legal, tax, currency, security, financial, and reporting requirements.
Can NetSuite inventory and warehouses be migrated?
Yes. Items, quantities, costs, lots, serials, locations, open demand, open supply, and warehouse relationships can be migrated when source data is available and reconciled.
Can open AR and AP be migrated?
Yes. Open invoices, vendor bills, credits, payments, deposits, remaining balances, due dates, and applications can be migrated and reconciled in Acumatica.
Can BizTech rebuild our NetSuite integrations in Acumatica?
Yes. BizTech develops custom Acumatica integrations and also provides existing solutions for Amazon, Shopify, WooCommerce, Magento, PayPal, ShipHero, ShipStation, DSCO, CommerceHub, Salesforce, ServiceTitan, EDI, and other systems.
Why choose BizTech for a NetSuite replacement?
BizTech is an Acumatica Gold Partner combining ERP implementation, data migration, custom development, proprietary connectors, integration architecture, reporting, testing, training, and post-go-live support.
How Amazon FBA and FBM Data Flows into Acumatica ERP
August 6, 2026
How Shopify Data Flows into Acumatica ERP
August 5, 2026
How WooCommerce Data Flows into Acumatica ERP
August 4, 2026
How Amazon FBA and FBM Data Flows into Acumatica ERP
How Amazon FBA and FBM Data Flows into Acumatica ERP
Amazon order data flows into Acumatica ERP through the Biz-Tech Services Amazon Connector, which retrieves orders from Amazon into an intermediate server, imports the selected orders into Acumatica as sales orders or invoices, and then sends purchase order acknowledgements, fulfillment events, refunds, and inventory quantities back to Amazon. The connection is never direct. Every request travels through an intermediate server controlled by Biz-Tech Services, and the settings that govern that connection live on the Amazon Stores screen in Acumatica. Once those settings are in place, the Biz-Tech Services Acumatica Amazon connector handles two distinct fulfillment channels: Fulfillment by Merchant, or FBM, where your business ships the goods, and Fulfillment by Amazon, or FBA, where Amazon ships from its own fulfillment centers.
Those two channels take different paths through Acumatica, and understanding the difference is the key to using the Biz-Tech Services Acumatica Amazon connector well. FBM orders become sales orders that your warehouse picks, packs, ships, and invoices, with acknowledgements and fulfillment documents flowing back at each step. FBA records arrive as transfer orders, purchase receipts, and invoices, because the movement being recorded is a transfer of your stock into Amazon inventory rather than a shipment to a shopper. This article traces the whole path in the order the records travel, names the screens, tabs, buttons, and fields involved at each stage, and points out where users should look when something does not land as expected.
What the Amazon Connector for Acumatica Does
The Amazon Connector is an Acumatica ERP customization from Biz-Tech Services, Inc. that links Amazon, the e-commerce platform, with Acumatica enterprise resource planning. It is delivered as a customization project and must be installed on an Acumatica system carrying one of the supported licenses, PCSR, PERP, or SAAS.
The documented capabilities cover both directions of travel. Inbound, the Biz-Tech Services Acumatica Amazon connector imports Amazon orders as either sales order or invoice document types, creates the customer on the fly when that customer does not yet exist in Acumatica, imports sales tax, and imports payment information. Outbound, it sends purchase order acknowledgements, sends fulfillment documents when shipments are confirmed, and sends inventory status documents so Amazon sees the quantity your business actually has available. A cross-reference layer sits between the two systems and matches items, payments, and Ship Via values so that Amazon terminology resolves to Acumatica records instead of failing.
Several of the outbound actions can be run three ways: from the Actions menu on a single Sales Orders document, from a processing screen where many records are selected and pushed at once, or automatically. Acknowledgements can be sent automatically with a Success status, and fulfillment documents can be sent automatically when an invoice is prepared. That mix matters because a business running a handful of orders a day works differently from one running hundreds, and the same configuration supports both.
The Amazon Data Flow at a Glance
Before looking at individual screens, here is the path records travel through the Amazon Connector from setup to settlement of the last refund:
- Credentials are entered and tested on the Connection Settings tab of the Amazon Store screen, which confirms Acumatica can reach the Biz-Tech server that fronts Amazon.
- The rest of the Amazon Store screen defines behavior: FBM Settings and FBA settings tabs, plus Cross-Reference, Warehouse Details, Inventory Details, Carriers Code, Cancel Reasons, and Adjustment Reasons tabs.
- For FBM, the Get Orders button on the Import Amazon Orders screen pulls Amazon orders into a grid, filtered by Start Date and End Date, where they can be reviewed before anything is committed.
- The Import or Import All button turns the selected Amazon orders into Acumatica documents, applying the customer, item, tax, payment, and cross-reference rules configured on the store.
- Outbound acknowledgement is sent from the Sales Orders Actions menu or from the Export Amazon PO Acknowledgement processing screen, which pushes the acknowledgement through the Biz-Tech server to Amazon.
- Fulfillment follows the standard Acumatica chain, Create Shipment, Confirm Shipment, Prepare Invoice, and Release, with Prepare Invoice fulfilling the order in Amazon.
- For FBA, Import FBA Shipments creates transfer orders and purchase receipts as stock moves into Amazon fulfillment centers, while Import FBA Orders brings in the resulting FBA sales as invoices.
- Refunds travel back through Import Amazon Refunded Orders, which produces a customer refund payment or a credit memo depending on how far the original order had progressed.
- Inventory quantities travel outward from the Export Amazon Inventory Quantity screen, summed across the warehouses listed on the Warehouse Details tab.
FBA and FBM: Two Fulfillment Paths, One Amazon Connector
Fulfillment by Amazon is a service Amazon provides so sellers can streamline logistics and order fulfillment. Under FBA, sellers store their products in Amazon fulfillment centers, and Amazon handles the storage, packing, shipping, and customer service for those items. Fulfillment by Merchant is the opposite arrangement: the seller keeps the stock and ships the order. Because the physical goods behave differently, the Acumatica documents behave differently too, and the Biz-Tech Services Acumatica Amazon integrator keeps the two channels on separate tabs and separate processing screens.
The practical consequence is that FBM is an order-to-cash flow and FBA is partly an inventory-transfer flow. An FBM order becomes a sales order of the type configured on the FBM Settings tab, and your business creates the shipment, enters the tracking number, and confirms it. An FBA record set arrives in pieces: shipments of your stock into Amazon become transfer orders, deliveries become purchase receipts in the destination warehouse, and the actual FBA sales come in as invoices. FBA settings therefore include warehouse mapping and a Destination Order Type that has to be a Transfer order type, which has no equivalent on the FBM side.
Both channels can be reviewed together. The FBM and FBA Orders screen shows both kinds of order in one place, and the distinction between them is indicated by the Fulfillment channel field. When users are not sure which path a given order took through Acumatica, that field is the answer.
Stage One: Installing the Package and Connecting Acumatica to Amazon
The Biz-Tech Services Acumatica Amazon integration arrives as a customization project, a set of changes and additional files used to modify the Acumatica ERP application. Administrators import the deployment package, open it for editing in the Customization Project Editor if needed, validate it, and publish it for one tenant or several. Publishing uploads the package, creates the corresponding customization project, and saves it in the database. None of the Biz-Tech Services Acumatica Amazon connector screens exist until that happens.
What the Amazon Store screen identifies
The Amazon Store screen is the anchor record for everything else. Store Code is a lookup field that indicates the corresponding store, and Description describes it. The data on the General tab is provided automatically for the Store Code entered. When the Default Store checkbox is selected, that store appears automatically whenever a user opens a processing screen or a store screen and clicks into the Store code field. On an installation with a single marketplace this saves a click on every process; on an installation with several stores it prevents the more expensive mistake of running a process against the wrong marketplace.
Which credentials the Connection Settings tab holds
The Connection Settings tab uses the information specified on it to test whether Acumatica can connect to the Acumatica to Biz-Tech server. Get a successful test here before touching any other tab, because a failed import caused by a bad credential looks very similar to one caused by a bad mapping.
The fields on this tab are the OAuth and Amazon identifiers the intermediate server needs. Client ID is the identifier associated with an application that assists with client and server OAuth 2.0 authentication. Client secret is a secret known only to the application and the authorization server, and functions as the application own password. A refresh token is a special key that lets a client retrieve new access tokens without requiring the user to perform a complete login, which is what allows scheduled processes to run unattended. Marketplace is the store location, and AWS Regions are the physical locations where Amazon clusters data centers for application and service delivery in AWS Availability Zones.
The remaining values complete the picture. Consumer Key is the API key a service provider issues to a consumer, and it identifies that consumer. Consumer Secret is the consumer password, used along with the consumer key to request authorization to a user resources. External System Store ID is an identifier used to track data in relation to external systems integrated with the Amazon platform. Seller ID and MWS Auth Token are generated when the new developer authorization process is passed. If any of these are wrong, nothing downstream works.
Stage Two: FBM Settings That Govern How Amazon Orders Import
The FBM Settings tab on the Amazon Store screen decides what an imported Amazon order looks like in Acumatica. Import Amazon Orders specifies where to import the Amazon orders in the Acumatica system, and Order Type is the default type of order the Biz-Tech Services Acumatica Amazon integration creates. The Last Imported Order Date field shows the date the latest order was imported, which is the quickest sanity check that the flow is still running. When the Send Email Notifications for Errors checkbox is selected, the Biz-Tech Services Acumatica Amazon connector sends email notifications listing the Order IDs that hit errors, so nobody has to sit watching a grid.
How customer records are created from Amazon orders
When the Import Customer checkbox is selected, the Biz-Tech Services Acumatica Amazon integration imports the customer information from Amazon into a new customer record in Acumatica. When it is not selected, orders are imported against the default customer instead. This is a real business decision: importing customers gives your business a per-shopper record and history, while a single default customer keeps the customer ledger compact when shoppers are not accounts you intend to manage.
Two checkboxes control addresses. Override Ship Address Information from Amazon Order imports the address of the location the order is going to be shipped to from Amazon. Override Bill Address Information from Amazon Order imports the address information of whoever will pay the order bill from Amazon. Where the Amazon-supplied address must win over whatever is stored on the Acumatica customer, these are the settings that make it win.
How Amazon items are matched or created on import
The Import Item checkbox tells the Biz-Tech Services Acumatica Amazon integrator to import new product information from Amazon into Acumatica when that product does not yet exist in the Acumatica system. If the checkbox is not selected and an unknown item arrives, an error will occur during integration. That single checkbox is behind a large share of first-week import failures, so it is worth checking first when imports stop.
There is a documented nuance about descriptions. If the item already exists on the Stock Items screen, the Biz-Tech Services Acumatica Amazon connector does not update its description, but it does set the Amazon item title as the description in the Line description on the Sales Orders screen. The Acumatica master record keeps your naming, and the order line carries the marketplace wording that a shopper would quote.
Warehouse ID is the default warehouse set on imported orders, and UOM, the unit of measure, is used to quantify the inventory items. When the Insert Item in Inventory Details Tab checkbox is selected, items are retrieved into the Inventory Details tab of the Amazon Store screen while orders are being imported, which builds the mapping table as a side effect of normal trading rather than as a separate data-entry project.
Tax and payment defaults applied during import
Three tax fields sit on the same tab. Taxable Category is used to create or edit the tax categories applied to products. Customer Tax Zone is the combined set of effective taxes for a zone, defined according to the locations of vendors or customers. Tax ID is the client tax identifier. Because the Biz-Tech Services Acumatica Amazon connector can import sales tax from Amazon, these defaults are what the imported tax lands against, and a missing tax zone is a common reason an otherwise valid Amazon order will not post.
Under Payment Options, Payment Method is the default payment method set for the new customer records generated in Acumatica from the Amazon orders. Cross-Reference options is the setting that selects which entities should be matched between Amazon and Acumatica during the transition, and it directly controls the next tab.
Cross-References, Warehouses, Carriers, and Reason Codes
Between the credentials and the processing screens sits a set of tabs whose only job is translation. They are unglamorous and they are where most integration problems are actually solved.
The Cross-Reference tab
On the Cross-Reference tab, the Field column selects the entity whose Amazon and Acumatica values should be matched, and only the entities selected under Cross-Reference Options appear in that drop-down. Amazon Value then specifies which Amazon value must match which Acumatica Value. The documented example to verify afterwards is Ship Via: after the Amazon order import process, the Ship Via value should be visible in the Delivery Settings area of the Shipping tab on the Sales Orders screen. If it is blank there, the cross-reference is the place to look, not the order.
The Warehouse Details tab
The Warehouse Details tab is where your business adds the warehouses that need to be in sync with Amazon. Two behaviors follow from it. If several warehouses are selected on this screen, the exported item quantity is the sum of quantities across those selected warehouses, so Amazon sees pooled availability rather than a single site. And depending on the drop-down value selected, On hand, Available, or Available for Shipment, that is the quantity basis synced from Acumatica to Amazon. Choosing Available for Shipment rather than On hand is how your business avoids advertising stock that is already allocated.
The Inventory Details tab and SKU mapping
To upload a new SKU for an Amazon item, the mapping is created on the Inventory Details tab of the Amazon Store screen. If Import Item is checked on the import settings and an order is imported, the connector generates an Acumatica Inventory ID based on the SKU. To update the SKU afterwards, change the SKU for the existing item on the Inventory Details tab and import again, and no new item is created in Acumatica. That is the documented way to correct a mapping without leaving duplicate inventory IDs behind.
One pricing rule is worth committing to memory: during order import the Biz-Tech Services Acumatica Amazon connector takes the Amazon item price rather than the mapped Acumatica item price. The Amazon order is the commercial record of what the shopper paid, so Acumatica records that number rather than your list price.
Four buttons populate this tab. Get Product by ASIN displays the Amazon item in Inventory Details by its ASIN. Get Product by SELLERSKU does the same by SKU. Load FBA Products loads and displays all Amazon products in the store. Sync From Amazon takes a loaded FBA item and creates that item in Acumatica via the product SKU, which is the fastest way to seed Acumatica with an existing Amazon catalog rather than typing it.
Carriers Code, Cancel Reasons, and Adjustment Reasons
The Carriers Code tab matches Amazon carrier details to the Acumatica Ship Via carrier. The Cancel Reasons tab holds the order cancel reasons, and a cancellation reason must be selected while cancelling orders, so an empty tab blocks cancellations. The Adjustment Reasons tab is populated the same way and its values are required for refunding Amazon orders. Both reason lists can be imported or exported as an Excel file, which is the practical way to load them once and reuse them across tenants.
Inbound: How Amazon FBM Orders Become Acumatica Documents
The Import Amazon Orders screen is the inbound gate for FBM. The user indicates the Store Code, and the screen retrieves data for that store: it pulls as many orders into Acumatica as exist in the selected period and displays all of them in the table, so nothing is committed on retrieval alone.
Retrieving Amazon orders with Get Orders
Step one is clicking the Get Orders button to retrieve orders from Amazon. After the button is clicked a timer indicates the elapsed time until the process is complete, and a user can cancel the retrieval by clicking the loading icon next to the timer. The Start Date and End Date fields filter the data retrieval, which is how your business avoids dragging months of history back on a routine run. Step two is reviewing the retrieved orders to decide which ones need to be imported.
Reviewing an order before importing it
Clicking the Order Number opens the corresponding order in a pop-up window, and the most important information is shown on the Amazon Orders screen. This is also the first place errors surface: if an error appears while importing a corresponding order, the error message is displayed on this screen and explains what should be fixed and in which system. That last part matters, because roughly half of import problems are Amazon-side data and half are missing Acumatica configuration.
Running the import
Step four is selecting the orders that require import. Step five is clicking the Import button to begin the import process, or the Import All button to import every order in the grid. After the Import button is pressed, unselected orders are filtered off the screen so the grid shows only what is being worked. A user can cancel the process of importing orders by clicking close.
If there is an error while processing an order, the error displays on the grid line corresponding to that order, and a user should hover the cursor over the red cross to see additional information about it. For deeper detail, a user can open Tools and then Trace.
Outbound: Sending Amazon PO Acknowledgements from Acumatica
Once an Amazon order exists in Acumatica as a sales order, the first thing that travels back to Amazon is the purchase order acknowledgement. There are two documented ways to export it: one at a time, or several at once.
Acknowledging a single Amazon order
Choose the required order on the Sales Orders screen, click the Actions button, and choose the Send Acknowledgement to Amazon option. After the action finishes, the Acknowledgement status changes to closed. That status change on the sales order is the confirmation that Amazon has the acknowledgement, and it is the field to check when someone asks whether an order was acknowledged.
Acknowledging many Amazon orders at once
For volume, open Export Amazon PO Acknowledgement from Process Orders. This screen sends an API request to the Biz-Tech server, and the server in turn sends a request to the Amazon system to create the acknowledgement for the order. Choose the required orders by checking their checkboxes and press the Process button. The Biz-Tech Services Acumatica Amazon connector can also send acknowledgements automatically with a Success status.
Acknowledging with a Failure status to cancel
If an order must be cancelled, the Amazon acknowledgement is sent with a Failure status instead, and the Cancel reason field is required. The alternative route is Manually export Amazon PO Acknowledgement from Process Orders: choose the required order by checking its checkbox, click the Set Status Failure button, choose the Cancel Reason from the column below, press Save, and then Send Acknowledgement. This is why the Cancel Reasons tab has to be populated during setup; without it the cancellation cannot be completed.
Reflecting an Amazon-side cancellation back in Acumatica
The other direction is also documented. To cancel an order that already exists in Acumatica, cancel the order in Amazon, then open the Amazon Orders screen and press the Update Order button. That button updates the Amazon status in Acumatica so the two systems agree. Without it, Acumatica keeps working an order Amazon has already killed.
Outbound: Exporting Amazon Fulfillments from Shipments and Invoices
After the acknowledgement, fulfillment follows the ordinary Acumatica shipping chain, with the connector attached at two points.
From the Actions menu on the sales order, click Create Shipment. The user is then redirected to the Shipments screen. There, fill in Ship Via, add a Packages record, set a tracking number, and click Confirm Shipment.
Then click Prepare Invoice. Preparing the invoice is what fulfills the exact Amazon order: it sends an API request to the Biz-Tech server, and the server sends an API request to fulfill the order in the Amazon system. The same action can be performed in bulk from the Export Amazon Fulfillments screen by choosing the required shipments and pressing Process. The final step is navigating to the Invoice from Sales Orders and releasing the required invoice, which closes the accounting side of the transaction in Acumatica.
Refunds: Credit Memos and Imported Amazon Refunded Orders
Refunds move in both directions too, and the connector treats a refund initiated in Acumatica differently from a refund initiated in Amazon.
Refunding from Acumatica with a credit memo
To refund an order from the Acumatica side, open Invoices and Memos from Receivables, choose the required invoice, click Actions, and then Reverse. Fill in the Adjustment Reason, save the changes, and release. Releasing sends an API request to the Biz-Tech server, and the server sends an API request to refund the order in the Amazon system. The Adjustment Reason is mandatory, which is the reason the Adjustment Reasons tab is part of store setup.
Importing refunds that started in Amazon
The Import Amazon Refunded Orders screen brings refunds that originated in Amazon back into Acumatica. Press the Get Orders button to load refunded orders, with a timer showing elapsed time until the process is complete. The refunded Amazon orders are displayed on the Amazon Refund screen. Choose the required orders by checking their checkboxes and press Process, or click Process All to import every refunded order shown.
How the connector handles each refund case
What the Biz-Tech Services Acumatica Amazon integrator connector does next depends entirely on how far the original order had progressed, and five cases are defined. In case one the refunded order is still only a sales order with no fulfillment. If it consists of one item, processing creates a Payment of the Customer Refund type, attaches it on the Payments tab, sets the refunded amount, and closes the order; following the Reference number shows that payment and the refunded amount on the Application History tab. The sales order status changes to Canceled and all lines are deleted.
Still within case one, if the order consists of several items, the refunded quantity is reduced from the order quantity and the system creates a Payment document attached on the Payments tab for the refunded items, while the order status remains Open. A partial refund therefore leaves a working order behind rather than cancelling the whole thing.
Case two covers a shipment that has been created but not confirmed: pressing Process finds it, deletes it, and then proceeds with the case one actions above. Case three covers a confirmed shipment, where the system creates a Credit Memo and attaches the Reference number with the Customer Refund type to Applications. Case four, an invoice prepared but not released, produces the same Credit Memo.
Case five is the fully posted scenario, where the invoice has already been released. Here the system reverses the invoice and generates a Credit Memo with a Customer Refund type Reference number attached to Applications. In every case, once the actions complete, the Processed checkbox on the Refunds tab is automatically checked on the Amazon Orders screen for the corresponding order, which means the process is over and the order is Closed. The credit memo itself is created in the Invoices screen of Sales Orders.
Item and Inventory Quantity Sync from Acumatica to Amazon
The Export Amazon Inventory Quantity screen syncs Acumatica and Amazon inventory quantities through the Biz-Tech server. Its behavior is governed by a checkbox on each line, and the distinction is easy to miss. If the checkbox is not selected, the Sync action updates the Amazon inventory quantity based on the number in the Quantity column, that is, the Acumatica quantity. If a user wants to send a different number to Amazon, change the value in the Amazon Quantity column, check the checkbox, and then press the Sync button, and the Amazon inventory quantity is updated to that value.
That override is useful when your business deliberately holds stock back from the marketplace, and it is also the reason listed availability can drift from Acumatica availability without anyone noticing. The quantity sent is still governed by the Warehouse Details tab: the sum across the selected warehouses, on the On hand, Available, or Available for Shipment basis chosen there.
FBA Settings: Configuring Fulfillment by Amazon in Acumatica
The Amazon Store screen carries a tab that provides access to all the settings for Amazon FBA orders. It is organized into order options, warehouse mapping, shipment options, customer information, and a payment option, and each group maps onto a distinct part of the FBA flow.
FBA Default Order Options
Invoice Type is the document created after an Amazon FBA order is received and imported, because an FBA order is imported as an invoice in Acumatica rather than as a sales order to be picked. Begin Order date filters the data retrieval, and Last Imported Order Date records when the last order was imported. Below the dates is a table for mapping Acumatica statuses to Amazon order statuses by selecting the corresponding status, so the connector knows which Amazon states are meaningful in your Acumatica workflow. To retrieve and import an order, the corresponding Order Status checkbox must be selected.
FBA Warehouse and fulfillment center mapping
Destination warehouse sets up the warehouse in Acumatica where Amazon goods or products are intended to be sent or delivered. When the Enable Ship from Mapping checkbox is selected, a mapping section opens between the Amazon Fulfillment Center and the Ship-from Warehouse ID, letting your business map an Amazon fulfillment center to an Acumatica warehouse ID and determine which warehouse ships product to the destination warehouse. If the checkbox is not selected, the section disappears and the single value in the Ship from Warehouse ID field is used instead. Businesses shipping into several Amazon fulfillment centers from several of their own sites need the mapping; a single-warehouse seller does not.
FBA Default Shipment Options
Destination Order Type should be populated with the Transfer order type, because all FBA orders need to be created using that specific order type. A Destination Order Type checkbox is included for transfer order types, and when it is selected the Order Type field is disabled, indicating that it is an Amazon FBA order type. One configuration rule is stated explicitly and is easy to trip over: the same order type can only be configured in one store and cannot be repeated in other stores.
Two checkboxes decide what is retrieved. Select Shipments imports FBA shipments, and Select Deliveries imports FBA deliveries. Two date fields report progress: Last Imported Shipment Date is the date the last shipment was imported from Amazon into an Acumatica transfer order, and Last Imported Deliveries Date is the date the last delivery was imported into an Acumatica purchase receipt. Below the dates, a table displays the corresponding Amazon shipment status to be imported into Acumatica.
Two more checkboxes change the resulting documents. When Release PO Receipt During FBA Shipment Import is selected, the shipment is imported as already released into the purchase receipt, which removes a manual release step for businesses that trust the Amazon numbers. Override FBA Shipment bill address information controls whether the order import overrides the customer addresses and sets the Acumatica order address on the sales order, or sets the customer billing address instead.
FBA customer and payment options
The Customer field sets the default customer used during the order import process from Amazon to Acumatica, and it is required for the Amazon orders import process. Under FBA Payment Option, selecting Import Amazon FBA Payment opens a further field for the payment method name, so a payment method can be set up and imported for the FBA order.
The FBA Process Flow: Shipments, Transfers, Deliveries, and Orders
The FBA flow in Acumatica is best read as two tracks. One track moves your stock into Amazon fulfillment centers and keeps the inventory numbers honest. The other track brings the resulting Amazon sales in as invoices.
Importing FBA shipments as transfer orders
To transfer and update items in a single shipment, the FBA shipments must first be pulled from Amazon Seller Central into Acumatica. When a shipment is imported, it creates a sales order with the Transfer order type already selected and set up in the FBA store. The grid displays the destination warehouse where the item will be received, and the sales order line shows the warehouse the item should be transferred from. Selecting the pre-configured Transfer order type established in the store displays the store code on the Sales Orders screen, which is how a user tells an FBA transfer apart from an ordinary internal one.
Updating warehouses with Update In
Upon confirming the shipment of the transfer order and clicking the Update In button, the system updates the warehouse by transferring items from the source warehouse to the destination warehouse. This is the step where Acumatica inventory finally reflects that the goods are in Amazon custody rather than on your own shelves.
Importing FBA deliveries as purchase receipts
After the items have been updated in the warehouses and the shipments are closed in Seller Central, go to the Import FBA Deliveries screen to retrieve all shipments. They are then displayed on the Purchase Receipt screen and are already in the destination warehouse. Following the purchase order release process, the quantity in the destination warehouse is updated and displayed.
Quantity rules on the Import FBA Shipments screen
The Import FBA Shipments screen handles the retrieval and importation of all shipments from Amazon into Acumatica and creates a purchase receipt based on the received quantity of the shipment. Three quantity outcomes are documented. If the received and shipped quantities are equal, the order imports without any issues. If the received quantity is smaller than the shipped quantity, the order still imports. If the received quantity exceeds the shipped quantity, an error message appears stating that the received quantity is greater than the shipped quantity. To prevent that, item quantities need to be adjusted on the FBA Shipments screen before importing.
Importing the FBA orders themselves
The Import FBA Orders screen gets and imports all Amazon FBA orders into Acumatica according to the dates and statuses configured on the store, and after importing it creates a sales order invoice. Imported FBA orders are displayed on the Invoices screen of Sales Orders, which is where users should look for them rather than in an open sales order list.
Where to Monitor Amazon Results in Acumatica
Most support questions about an Biz-Tech Services Acumatica Amazon integration reduce to one question: did the record make it, and if not, where did it stop? These are the exact places in Acumatica to look:
- Import Amazon Orders grid, where a red cross on an order line signals a failure; hover over it for detail, or open Tools and then Trace for more.
- Amazon Orders screen, opened by clicking the Order Number, which shows the key order information and the error message explaining what should be fixed and in which system.
- Email notifications listing Order IDs with errors, if the Send Email Notifications for Errors checkbox is selected on FBM Settings.
- Last Imported Order Date on the FBM Settings tab, and its equivalent on FBA settings, to confirm the flow is still running.
- Acknowledgement status on the sales order, which changes to closed once Send Acknowledgement to Amazon has finished.
- The Delivery Settings area of the Shipping tab on Sales Orders, where the cross-referenced Ship Via value should appear after import.
- Payments tab and Application History tab, where a Customer Refund payment and the refunded amount are recorded against the Reference number.
- Refunds tab on the Amazon Orders screen, where the Processed checkbox is checked automatically once a refund is fully handled and the order is Closed.
- Invoices screen of Sales Orders, where credit memos from refunds and imported FBA order invoices both appear.
- FBA Shipments screen, a set of generic inquiries giving compact information about shipments in both Acumatica and Amazon.
- FBA Destination Warehouse Quantities screen, which tracks warehouse updates and shows item quantities in both the destination warehouse and the current warehouse.
- FBM and FBA Orders screen, where the Fulfillment channel field identifies which channel each order came through.
Amazon Acumatica Integration: Frequently Asked Questions
What is the difference between FBA and FBM in the Amazon Connector for Acumatica?
FBM, Fulfillment by Merchant, means your business ships the order, so the Biz-Tech Services Acumatica Amazon integrator imports it as a sales order and you run Create Shipment, Confirm Shipment, and Prepare Invoice, with the fulfillment event going back to Amazon. FBA, Fulfillment by Amazon, means your products sit in Amazon fulfillment centers and Amazon handles storage, packing, shipping, and customer service, so the Biz-Tech Services Acumatica Amazon connector imports FBA shipments as transfer orders, FBA deliveries as purchase receipts, and the FBA orders themselves as invoices. The two channels have separate settings tabs and separate processing screens, and the FBM and FBA Orders screen shows both, distinguished by the Fulfillment channel field.
Are Amazon orders imported into Acumatica as sales orders or as invoices?
Both are supported. The Biz-Tech Services Acumatica Amazon integration can import Amazon orders as either the sales order or the invoice document type, and the Order Type field on the FBM Settings tab sets the default for FBM. For FBA the answer is fixed: an imported Amazon FBA order becomes an invoice, controlled by the Invoice Type field on the FBA settings tab, and those invoices appear on the Invoices screen of Sales Orders.
Why does my Amazon order import fail with an item error?
The most likely cause is the Import Item checkbox on the Amazon Store screen. When it is selected, the Biz-Tech Services Acumatica Amazon integrator imports product information for items that do not yet exist in Acumatica; when it is not selected and an unknown Amazon item arrives, an error occurs during integration. Check that checkbox first, then check whether the SKU is mapped on the Inventory Details tab of the Amazon Store screen. The full error text is shown on the Amazon Orders screen and explains what should be fixed and in which system.
How do I see the exact error behind a failed Amazon order import?
There are three places, in increasing order of detail. On the Import Amazon Orders grid, hover the cursor over the red cross on the failing order line to see additional information. Click the Order Number to open the Amazon Orders screen, where the error message states what should be fixed and in which system. For anything still unclear, open Tools and then Trace for the underlying detail.
What does the error "Received quantity is greater than the shipped quantity" mean?
It appears on the Import FBA Shipments screen when the received quantity on an Amazon FBA shipment exceeds the quantity shipped, and it blocks the import. Equal received and shipped quantities import cleanly, and a received quantity lower than the shipped quantity still imports. To clear the error, adjust the item quantities on the FBA Shipments screen before importing again.
How do I cancel an Amazon order from Acumatica?
Send the Amazon acknowledgement with a Failure status and fill the required Cancel reason field. From Process Orders, open Manually export Amazon PO Acknowledgement, check the order, click Set Status Failure, choose the Cancel Reason, press Save, and then Send Acknowledgement. Cancel reasons must already exist on the Cancel Reasons tab of the Amazon Store screen, otherwise the cancellation cannot be completed. If the cancellation happened in Amazon instead, open the Amazon Orders screen and press Update Order to bring the Amazon status into Acumatica.
What happens when an Amazon order is refunded after the invoice was released?
That is case five of the refund logic. When you process the refunded order on the Import Amazon Refunded Orders screen, the system reverses the invoice and generates a Credit Memo carrying a Reference number of the Customer Refund type attached to Applications. Once the actions finish, the Processed checkbox on the Refunds tab of the Amazon Orders screen is checked automatically and the order is Closed. The credit memo itself is created on the Invoices screen of Sales Orders.
Work With the Biz-Tech Services Amazon Connector
Traced end to end, the flow is coherent: credentials on the Connection Settings tab open the channel to the Biz-Tech intermediate server, the FBM Settings and FBA settings tabs decide what imported records look like, the cross-reference, warehouse, carrier, and reason tabs translate Amazon values into Acumatica ones, and the processing screens move orders, acknowledgements, fulfillments, refunds, and quantities in the appropriate direction. FBM runs through sales orders, shipments, and invoices; FBA runs through transfer orders, purchase receipts, and invoices. When something goes wrong, the Amazon Orders screen, the red cross tooltip, the trace, and the Processed checkbox on the Refunds tab tell your business exactly where the record stopped.
If your business sells on Amazon and wants that activity landing in Acumatica ERP as accurate orders, shipments, invoices, refunds, and inventory quantities, the Biz-Tech Services Amazon Connector is built for exactly that. Visit https://biz-techservices.com to learn more about our Acumatica expertise or to schedule a personalized demonstration.
QuickBooks to Acumatica Migration Guide 2026 | Complete ERP Transition Guide
QuickBooks to Acumatica Migration Guide 2026: When to Upgrade, What It Costs, and How to Migrate Successfully
QuickBooks can be an excellent starting point for a small business. It helps companies establish financial discipline, manage invoices and bills, track income and expenses, and build a reliable accounting foundation without immediately taking on the cost and complexity of a complete enterprise resource planning system.
The problem is not that QuickBooks suddenly becomes “bad” when a company grows.
The problem is that a growing business eventually becomes more than an accounting process.
It develops multiple warehouses, new sales channels, more complex inventory, larger purchasing operations, project accounting requirements, manufacturing workflows, field operations, intercompany activity, eCommerce stores, marketplace orders, customer-specific pricing, shipping integrations, payment systems, and reporting demands that reach far beyond the general ledger.
At that stage, the company often begins using QuickBooks together with spreadsheets, inventory applications, CRM software, warehouse tools, eCommerce plugins, shipping platforms, payment portals, reporting databases, and custom workarounds. Every individual tool may solve a legitimate problem, but the complete operating environment becomes fragmented.
Orders are entered more than once. Inventory quantities differ between systems. Financial reports are correct only after manual reconciliation. Customer data is duplicated. Warehouse teams work from exports. Management dashboards are delayed. Employees spend more time moving information than using it.
This is usually the point when businesses begin researching:
- QuickBooks to Acumatica migration;
- Acumatica vs QuickBooks;
- QuickBooks Enterprise alternative;
- cloud ERP replacement for QuickBooks;
- how to migrate QuickBooks to Acumatica;
- Acumatica implementation partner;
- QuickBooks to ERP migration cost.
Moving from QuickBooks to Acumatica Cloud ERP is not simply an accounting software upgrade. It is a transition from an accounting-centered system to a connected business management platform that can unite financials, inventory, purchasing, sales orders, warehouses, manufacturing, projects, field service, CRM, reporting, eCommerce, payments, and integrations.
That transition can create significant operational value, but only when it is planned carefully.
A successful QuickBooks to Acumatica migration requires more than exporting lists and importing spreadsheets. The company must decide what data should move, what data should be cleaned, how the chart of accounts should evolve, how open receivables and payables should be represented, how inventory should be reconciled, how historical transactions should remain accessible, and how all external systems will connect to Acumatica after go-live.
As an Acumatica Gold Partner, BizTech helps companies manage the complete transition. Our work can include business process discovery, Acumatica implementation, QuickBooks data migration, financial reconciliation, inventory setup, custom development, eCommerce integration, marketplace automation, payment integration, testing, training, cutover planning, and post-go-live support.
This guide explains when a business should move beyond QuickBooks, how Acumatica differs from accounting software, what can be migrated, how the migration process works, what affects cost and timeline, which mistakes to avoid, and why the implementation partner matters.
QuickBooks Is Not One Product: Define the Source Before Planning the Migration
Before comparing QuickBooks with Acumatica, it is important to clarify what “QuickBooks” means in the context of the migration.
QuickBooks is a product family. A company may be using:
- QuickBooks Online;
- QuickBooks Online Advanced;
- QuickBooks Desktop;
- QuickBooks Desktop Enterprise;
- QuickBooks Enterprise with cloud hosting;
- industry-specific QuickBooks Enterprise configurations;
- QuickBooks connected to third-party inventory, payroll, eCommerce, CRM, reporting, or warehouse applications.
These environments are not identical.
QuickBooks Enterprise can provide more advanced functionality than entry-level accounting editions, including industry-specific tools, advanced inventory options, sales order fulfillment features, job costing, multi-company capabilities, and connected applications. Therefore, a fair Acumatica vs QuickBooks comparison should not pretend that every QuickBooks user has only basic bookkeeping features.
The real question is not whether QuickBooks has useful functionality.
The real question is whether the complete QuickBooks-centered environment still supports the company efficiently as complexity increases.
A migration assessment must identify:
- the exact QuickBooks product and edition;
- the version and hosting arrangement;
- the number of company files;
- the number of years of data;
- enabled inventory, payroll, project, and industry features;
- connected applications;
- custom reports and fields;
- manual spreadsheets used outside QuickBooks;
- operational processes that QuickBooks does not manage directly.
This source-system inventory affects the migration scope, data extraction method, field mapping, integration plan, timeline, testing, and cost.
A company moving from QuickBooks Online with limited inventory and one entity will have a different project from a distributor moving from QuickBooks Enterprise with several warehouses, advanced inventory, custom pricing, eCommerce applications, and years of transaction history.
When QuickBooks Stops Being Enough
QuickBooks often remains useful even after a company begins feeling operational pressure. Finance may still close the books. Invoices may still be generated. Bills may still be paid. Management may still receive financial statements.
The first signs of a problem usually appear outside accounting.
The warehouse may be working from a separate system. Sales representatives may not see reliable inventory. eCommerce orders may be imported manually. Customer service may need to check several applications before answering a question. Managers may wait for spreadsheets to understand profitability. Multiple company files may require manual consolidation. Manufacturing may depend on separate BOM, scheduling, or costing tools.
The accounting system continues working, but the operating model becomes increasingly difficult to manage.
Acumatica describes this transition in terms of manual processes, disconnected systems, fragmented data, limited real-time visibility, increasing financial complexity, multiple entities or locations, and business requirements that exceed entry-level accounting software.
The key distinction is this:
QuickBooks may still be capable of recording the financial result after work happens, while the business increasingly needs a system that also manages and coordinates the work itself.
That need becomes more urgent when employees are spending significant time on:
- re-entering transactions;
- exporting and merging spreadsheets;
- reconciling inventory between platforms;
- checking whether orders were shipped;
- matching online payments to invoices;
- consolidating company files;
- creating manual management reports;
- correcting inconsistent customer or item records;
- maintaining integrations that frequently fail.
At that point, continuing to add isolated tools can cost more than moving to a connected ERP platform.
Acumatica vs QuickBooks: Accounting Software vs a Connected ERP Platform
The most useful comparison is not “small software vs large software.” It is a comparison of system roles.
QuickBooks is primarily recognized as accounting software, although advanced QuickBooks editions can extend into inventory, order management, job costing, multi-company operations, and industry-specific use cases.
Acumatica is a complete cloud ERP and business management platform designed to connect financial activity with operational processes.
| Business area | QuickBooks-centered environment | Acumatica Cloud ERP |
|---|---|---|
| Financial management | Strong accounting foundation; capabilities vary by edition | Financial management connected directly to operations, projects, inventory, and industry workflows |
| Inventory | Available in selected editions and configurations; advanced requirements may involve add-ons | Integrated inventory, warehouses, locations, allocations, availability, purchasing, sales, and financial posting |
| Distribution | Can support selected order and inventory workflows, often with connected applications | End-to-end distribution management with purchasing, inventory, sales orders, fulfillment, pricing, and reporting |
| Manufacturing | QuickBooks Enterprise provides manufacturing and wholesale features, but complex production may require additional systems | BOMs, routing, production management, MRP, planning, costing, engineering changes, and shop-floor capabilities |
| Construction and projects | Job costing and project features vary by edition; broader field and project workflows may be external | Project accounting, job costing, commitments, change orders, billing, field collaboration, and project reporting |
| CRM | Frequently managed through another application | CRM connected with customers, opportunities, orders, invoices, service, and financial history |
| eCommerce and marketplaces | Typically connected through applications, imports, or middleware | Can serve as the central ERP behind commerce connectors, orders, inventory, payments, fulfillment, refunds, and reporting |
| Workflow automation | Often dependent on edition, add-ons, or external automation | Configurable workflows, business events, approvals, notifications, APIs, webhooks, and custom automation |
| Reporting | Strong accounting reports; cross-system operational reporting may require exports or external tools | Financial reports, Generic Inquiries, dashboards, role-based analytics, operational KPIs, and BI integrations |
| User access | User allowances and roles depend on the QuickBooks product and subscription | Acumatica promotes unlimited user access with pricing based on applications and resource consumption |
| System architecture | Varies across Online, Desktop, Enterprise, hosting, and connected application environments | Unified cloud ERP platform with open APIs, extensibility, and industry editions |
The strongest reason to move is not that Acumatica contains more menu options.
It is that Acumatica can replace many disconnected handoffs with one governed operating model.
Twelve Signs Your Business Has Outgrown QuickBooks
A business should not migrate simply because it reached a certain revenue or employee number. Operational complexity is a better indicator than company size.
The following signs suggest that the organization should evaluate a move from QuickBooks to Acumatica.
1. Manual Data Entry Is Increasing Faster Than Revenue
Employees repeatedly enter orders, customers, inventory adjustments, payments, or shipping information into more than one application.
Growth should create more business activity, not an equal increase in administrative re-entry.
2. Excel Has Become a Parallel ERP
Spreadsheets are used to manage inventory, order status, purchasing, forecasts, production, projects, commissions, or management reporting.
Spreadsheets are useful analytical tools, but they become risky when they are the only place where critical operational truth exists.
3. Reports Are Correct Only After Manual Reconciliation
Management cannot rely on a dashboard without first waiting for finance or operations to combine information from several systems.
By the time the report is complete, the underlying business may already have changed.
4. Inventory Is Managed Outside the Accounting System
Warehouse quantities, allocations, serial or lot information, reorder decisions, or fulfillment status are controlled by another application or spreadsheet.
This often creates disagreements between physical stock, operational systems, and accounting records.
5. The Company Operates Several Locations, Entities, or Warehouses
Multiple QuickBooks company files, manual consolidations, intercompany spreadsheets, and inconsistent processes make financial and operational control increasingly difficult.
6. Orders Come from Several Sales Channels
The business receives orders through direct sales, Shopify, WooCommerce, Amazon, Magento, retailers, EDI networks, or marketplaces.
Manual imports and fragmented integrations increase the risk of duplicate orders, incorrect taxes, delayed fulfillment, and inventory overselling.
7. Customer Data Is Fragmented
Sales, finance, service, eCommerce, and warehouse teams each see a different version of the customer.
A connected ERP should show quotes, orders, invoices, payments, service history, shipments, returns, and project activity in one environment.
8. Profitability Is Difficult to Measure
The company can see revenue but struggles to measure true margin by product, customer, channel, warehouse, project, or job.
This is especially common when fulfillment, fees, returns, labor, and inventory costs live outside the accounting system.
9. Financial Close Takes Too Long
Finance must reconcile eCommerce systems, inventory applications, payment processors, project tools, and spreadsheets before closing the period.
A connected ERP can reduce the number of manual reconciliations required.
10. Integrations Frequently Break or Require Manual Supervision
Connected apps may work independently but lack centralized error handling, audit history, retry logic, or consistent mapping.
Employees begin monitoring integrations manually and repairing data after failures.
11. More Administrative Headcount Is Needed to Maintain the Same Process
The company adds staff primarily to copy data, reconcile systems, prepare reports, and manage exceptions.
ERP automation should allow transaction volume to grow faster than administrative workload.
12. Business Decisions Are Being Limited by the Current System
The company avoids opening a new warehouse, adding an entity, expanding eCommerce, introducing manufacturing, or changing processes because the existing software environment cannot support the change cleanly.
When the system begins determining strategy, the business has likely outgrown it.
What Businesses Gain by Moving from QuickBooks to Acumatica
A successful migration should create measurable improvements, not merely replace one interface with another.
The major benefits can include:
One Source of Financial and Operational Truth
Financial activity, inventory, purchasing, sales orders, projects, manufacturing, service, commerce, and reporting can operate from a shared data model.
Real-Time Inventory Visibility
Users can see quantities by warehouse and location, availability, allocations, purchase orders, sales demand, and transaction history without reconciling separate tools.
Faster and More Reliable Reporting
Dashboards and reports can use live ERP data rather than waiting for manual consolidation.
Workflow Automation
Approvals, notifications, document creation, synchronization, and exception handling can be automated.
Broad User Access
Acumatica’s unlimited user philosophy can make it easier to include warehouse users, managers, project teams, customer service, and other departments.
Connected eCommerce and Marketplace Operations
Acumatica can become the ERP foundation behind Shopify, WooCommerce, Amazon, Magento, retail networks, shipping systems, warehouses, and payment providers.
Scalable Industry Functionality
The organization can expand into distribution, manufacturing, construction, project accounting, field service, CRM, and other applications without rebuilding its entire system architecture.
Open Integration Architecture
APIs, webhooks, import scenarios, business events, and custom extensions support connected operations.
Stronger Controls and Auditability
Roles, approvals, document history, transaction links, and workflow records improve accountability.
A Platform for Future Growth
The migration creates a foundation for new companies, locations, channels, products, integrations, and automation.
What Data Can Be Migrated from QuickBooks to Acumatica?
Most essential business data can be migrated, but the exact scope depends on the QuickBooks product, data quality, Acumatica configuration, and historical requirements.
Common migration categories include:
Financial Structure
- chart of accounts;
- account types;
- departments, classes, or dimensions;
- opening general ledger balances;
- financial periods;
- tax settings;
- currencies;
- company and branch relationships.
Customers and Receivables
- customer records;
- billing and shipping addresses;
- contacts;
- payment terms;
- tax information;
- credit limits;
- open invoices;
- credit memos;
- unapplied payments;
- customer balances;
- aging details.
Vendors and Payables
- vendor records;
- addresses and contacts;
- payment terms;
- tax identifiers;
- open bills;
- vendor credits;
- unapplied payments;
- vendor balances;
- aging details.
Inventory and Product Data
- inventory items;
- non-stock items;
- SKUs;
- descriptions;
- item classes;
- units of measure;
- cost information;
- sales prices;
- vendor relationships;
- warehouse assignments;
- opening quantities;
- lot or serial details where available and required;
- reorder information;
- assemblies or product structures where mapping is practical.
Open Operational Documents
- open sales orders;
- open purchase orders;
- open estimates or quotes;
- open projects or jobs;
- customer deposits;
- vendor prepayments;
- unshipped or partially fulfilled documents.
Historical Transactions
Depending on strategy, historical data may include:
- general ledger transactions;
- sales invoices and payments;
- vendor bills and payments;
- inventory transactions;
- sales and purchase history;
- project or job history;
- bank activity;
- attachments and source documents.
Not every field or relationship transfers directly. Some data must be transformed to fit the new Acumatica design.
What Data Should Not Be Migrated Automatically?
A migration is an opportunity to improve data quality.
Moving every historical record without evaluation can transfer years of errors and obsolete structures into the new ERP.
Data that should be reviewed carefully includes:
Duplicate Customers and Vendors
The same organization may appear several times under different names, spellings, addresses, or company files.
Duplicates should be identified and consolidated before import.
Inactive or Obsolete Records
Old customers, discontinued vendors, obsolete products, inactive accounts, and expired projects may not belong in the production ERP.
Some records may be retained in an archive rather than migrated as active master data.
Unreconciled Financial Balances
If the source books do not reconcile, importing the same values does not solve the problem.
Financial differences should be investigated and approved before opening balances are loaded.
Unreliable Inventory Quantities
An inaccurate source quantity should not become the opening quantity in Acumatica.
Physical counts and reconciliation may be required before cutover.
Legacy Custom Fields Without Current Business Value
Some fields exist only because of old workarounds. The business should confirm whether they still support a real process.
Unnecessary Transaction Detail
A company may not need every historical line in the live ERP. Summary balances, limited history, or an archive may provide better value.
Old Workarounds
Spreadsheets and coding conventions created to overcome QuickBooks limitations should not automatically define the Acumatica design.
The migration should preserve business requirements, not unnecessary constraints.
The QuickBooks to Acumatica Migration Process
A structured migration reduces risk and creates clear approval points.
Phase 1: Business Discovery
The project begins with understanding the company, not exporting data.
BizTech reviews:
- business model and industry;
- QuickBooks edition and version;
- company files;
- entities, branches, and locations;
- financial processes;
- sales and purchasing workflows;
- inventory and warehouse operations;
- manufacturing, construction, service, or project requirements;
- eCommerce and marketplace channels;
- payment and shipping systems;
- management reporting;
- growth plans.
The output is a documented view of the current state and target operating model.
Phase 2: Data Audit
The team evaluates:
- data sources;
- record volumes;
- duplicates;
- missing fields;
- custom fields;
- historical depth;
- open balances;
- inventory accuracy;
- attachments;
- reconciliation status.
The audit determines what can be migrated directly, what requires transformation, and what should remain archived.
Phase 3: Acumatica Solution Architecture
The target design may define:
- companies and branches;
- chart of accounts;
- subaccounts and reporting dimensions;
- customer and vendor classes;
- item classes;
- warehouses and locations;
- order types;
- tax configuration;
- security roles;
- approval workflows;
- required applications;
- integration architecture;
- reporting structure.
Data mapping cannot be finalized until the target structure is approved.
Phase 4: Data Cleansing and Transformation
Source records are standardized and prepared.
Activities may include:
- merging duplicates;
- standardizing names and addresses;
- normalizing item IDs;
- mapping accounts;
- assigning customer, vendor, and item classes;
- mapping units of measure;
- defining default warehouses;
- reconciling open balances;
- removing obsolete records;
- preparing import files.
Phase 5: Acumatica Configuration
BizTech configures the approved Acumatica environment, including financial management, inventory, sales, purchasing, projects, manufacturing, construction, CRM, commerce, and other required functionality.
Phase 6: Test Migration
A test migration validates the design before final cutover.
The team imports representative data and checks:
- record counts;
- field mappings;
- account balances;
- customer and vendor balances;
- inventory quantities and values;
- open documents;
- tax configuration;
- reporting;
- integration references.
A serious migration should not rely on the first import being correct.
Phase 7: Integrations and Automation
External systems are connected to the new Acumatica environment.
This may include Shopify, WooCommerce, Amazon, Magento, PayPal, ShipHero, ShipStation, Salesforce, ServiceTitan, DSCO, CommerceHub, EDI, tax systems, banks, BI platforms, and proprietary applications.
Phase 8: Financial and Operational Reconciliation
The team validates that Acumatica matches approved source totals.
Reconciliation may include:
- trial balance;
- accounts receivable aging;
- accounts payable aging;
- cash balances;
- inventory quantity and value;
- open sales orders;
- open purchase orders;
- project balances;
- fixed assets;
- retained earnings.
Phase 9: User Acceptance Testing
Users execute real business scenarios such as:
- creating and fulfilling a sales order;
- receiving a purchase order;
- processing an invoice and payment;
- handling a return or credit;
- moving inventory between warehouses;
- running production or project workflows;
- importing an eCommerce order;
- exporting shipment tracking;
- running financial and operational reports.
Phase 10: User Training
Training is delivered by role and process.
Users should learn not only which buttons to press, but also how the new process differs from QuickBooks and how to handle exceptions.
Phase 11: Final Cutover
The final cutover typically includes:
- source transaction freeze;
- final backups;
- final data extraction;
- production migration;
- reconciliation;
- integration activation;
- user access validation;
- go-live approval.
Phase 12: Post-Go-Live Support and Optimization
The team monitors transactions, user questions, integrations, reports, and performance.
Some process improvements are intentionally scheduled after users gain real production experience.
QuickBooks Chart of Accounts Migration to Acumatica
The chart of accounts should not always be copied exactly.
QuickBooks accounts may have been designed around the limitations of the previous system, reporting habits, classes, locations, or separate company files. Acumatica provides additional structural tools such as branches, subaccounts, and dimensions that can improve reporting without creating an unnecessarily large chart of accounts.
The migration process may include:
- reviewing existing accounts;
- removing duplicates and inactive accounts;
- mapping QuickBooks accounts to Acumatica accounts;
- converting classes, departments, or locations into subaccount segments or other dimensions;
- defining branch relationships;
- designing consolidated reporting;
- mapping retained earnings and control accounts;
- loading opening balances;
- validating the trial balance.
The goal is not to create the smallest chart of accounts or the largest one.
The goal is to create a structure that supports accurate posting, management reporting, auditability, and future growth.
QuickBooks Customer and Vendor Migration
Customer and vendor records influence sales, purchasing, payments, taxes, credit, shipping, integrations, and reporting.
A clean migration may include:
Customer Data
- customer ID and name;
- customer class;
- billing and shipping addresses;
- contacts and email addresses;
- payment terms;
- tax zones and exemptions;
- credit limits;
- preferred payment methods;
- salesperson assignments;
- eCommerce or marketplace identifiers;
- open balances.
Vendor Data
- vendor ID and name;
- vendor class;
- addresses and contacts;
- payment terms;
- tax information;
- payment instructions;
- currency;
- default expense or inventory relationships;
- open balances.
Duplicate Management
The business should define matching rules using names, addresses, tax IDs, email addresses, phone numbers, and legacy identifiers.
Duplicate records should not be merged automatically without business review because different records may represent separate legal entities, locations, or billing relationships.
QuickBooks Inventory Migration to Acumatica
Inventory migration is usually more complex than customer or vendor migration because quantities, values, units, locations, costs, and operational status must agree.
The migration may include:
- inventory and non-stock items;
- SKUs and alternate IDs;
- item classes;
- descriptions;
- units of measure;
- sales and purchase units;
- warehouses;
- warehouse locations;
- opening quantities;
- inventory value;
- standard, average, or other costing considerations;
- lot and serial information;
- vendor item relationships;
- sales prices;
- reorder points;
- safety stock;
- lead times;
- product attributes;
- eCommerce and marketplace references.
Inventory Reconciliation
Before final migration, the business should compare:
- QuickBooks quantities;
- warehouse system quantities;
- eCommerce availability;
- physical inventory;
- inventory value in the general ledger.
If these sources disagree, the company must approve the authoritative quantity and value before go-live.
Assemblies and Manufacturing Data
QuickBooks assemblies may need to be transformed into Acumatica bills of material, kit specifications, or other structures depending on the target manufacturing and inventory design.
This is not always a one-to-one field import. Routing, labor, overhead, scrap, revisions, and planning rules may need to be designed separately.
Migrating Open Accounts Receivable and Accounts Payable
Open AR and AP documents must be migrated carefully because they affect cash flow, aging, customer and vendor balances, payment application, and the opening trial balance.
Open Accounts Receivable
The migration may include:
- customer invoices;
- credit memos;
- unapplied payments;
- deposits;
- document dates;
- due dates;
- payment terms;
- reference numbers;
- remaining balances;
- applications between payments and invoices.
Open Accounts Payable
The migration may include:
- vendor bills;
- vendor credits;
- prepayments;
- unapplied payments;
- document dates;
- due dates;
- payment terms;
- reference numbers;
- remaining balances.
Reconciliation Requirements
After import:
- AR aging must match the approved source aging;
- AP aging must match the approved source aging;
- customer and vendor totals must agree with control accounts;
- unapplied payments must remain traceable;
- opening balances must not duplicate migrated documents.
This is one of the most important checkpoints in the migration.
Should Historical QuickBooks Transactions Be Migrated?
There are three common strategies.
Strategy 1: Full Detailed Historical Migration
The company migrates several years of transaction-level history into Acumatica.
Advantages:
- users can research history in one system;
- comparative reporting may be easier;
- customer, vendor, and item history remains directly accessible;
- the legacy system may be retired more completely.
Disadvantages:
- higher cost and longer timeline;
- more field mapping and data transformation;
- greater reconciliation effort;
- legacy errors and structures are more likely to be transferred;
- some transaction relationships may not map perfectly.
Strategy 2: Limited Historical Migration
The company migrates selected periods, summarized history, or only data needed for operational continuity.
This approach balances accessibility and cost.
Strategy 3: Opening Balances Plus Legacy Archive
Acumatica begins with clean master data, opening balances, and open documents. Detailed history remains in QuickBooks, a reporting database, PDF archive, or other controlled repository.
This is often the most efficient approach, but the business must maintain reliable historical access and define retention responsibilities.
How to Choose
The decision should consider:
- audit requirements;
- tax retention requirements;
- customer service needs;
- warranty and product history;
- project history;
- comparative reporting;
- legacy licensing cost;
- migration budget;
- data quality.
More historical data is not automatically better.
Useful, reliable, and accessible history is better.
Connecting Acumatica to the Systems QuickBooks Could Not Manage Centrally
Many companies do not migrate from QuickBooks alone. They migrate from an ecosystem built around QuickBooks.
The complete source environment may include:
- online stores;
- marketplaces;
- warehouse management systems;
- shipping platforms;
- payment processors;
- CRM systems;
- retailer networks;
- EDI platforms;
- tax applications;
- BI tools;
- custom databases.
The migration plan must decide whether each system will:
- be replaced by Acumatica functionality;
- remain and integrate with Acumatica;
- be replaced by another specialized application;
- be retired after data migration.
BizTech develops and implements Acumatica solutions for many of these connected workflows.
Amazon and Acumatica
The BizTech Amazon Connector can support Amazon FBA and FBM orders, acknowledgments, fulfillment updates, tracking, inventory synchronization, warehouse mapping, payments, taxes, and refunds.
Shopify and Acumatica
The BizTech Shopify Connector can support order import, B2B workflows, items, customers, locations, warehouses, inventory, pricing, images, attributes, metafields, fulfillment, and refunds.
WooCommerce and Acumatica
The BizTech WooCommerce Connector can synchronize orders, customers, products, categories, taxes, inventory, payments, fulfillment, and tracking.
Magento and Acumatica
The BizTech Magento Connector can synchronize orders, customers, items, pricing, categories, images, inventory, fulfillment, and refunds.
PayPal and Acumatica
The BizTech PayPal Integration can support PayPal invoice creation, payment status synchronization, cancellations, refunds, transaction visibility, and customer payment links.
Warehouse and Shipping Systems
BizTech solutions can connect Acumatica with:
- ShipHero;
- ShipStation;
- other warehouse, fulfillment, and shipping platforms through custom APIs.
CRM and Field Service
BizTech supports integrations including:
- Salesforce;
- ServiceTitan;
- custom CRM and service applications.
Retail Networks and EDI
BizTech provides solutions for:
- DSCO;
- CommerceHub;
- EZCom EDI;
- custom EDI and retailer workflows.
A migration is successful only when these connected processes are included in the target architecture.
QuickBooks to Acumatica Migration Cost
There is no fixed migration price that applies to every company.
The cost depends on:
- QuickBooks product and edition;
- number of company files;
- number of entities and branches;
- years of history;
- record volume;
- data quality;
- inventory complexity;
- open documents;
- required Acumatica applications;
- integrations;
- custom fields and workflows;
- reporting requirements;
- testing;
- training;
- cutover support.
A complete budget usually contains:
| Cost category | Typical work |
|---|---|
| Acumatica software | Applications, resource tier, storage, and deployment model |
| Implementation | Discovery, architecture, configuration, testing, project management |
| Data migration | Extraction, cleansing, mapping, import, validation, reconciliation |
| Integrations | Commerce, marketplaces, payments, warehouses, shipping, CRM, EDI, APIs |
| Customization | Custom fields, screens, workflows, logic, actions, extensions |
| Reporting | Financial statements, dashboards, Generic Inquiries, BI integrations |
| Training | Role-based sessions, documentation, videos, adoption support |
| Post-go-live support | Monitoring, issue resolution, optimization, enhancements |
What Reduces Migration Cost?
- clean and reconciled source data;
- one QuickBooks company file;
- limited historical migration;
- clear process ownership;
- standard Acumatica configuration;
- existing BizTech connectors;
- fast client decisions;
- well-defined reporting requirements;
- realistic phased scope.
What Increases Migration Cost?
- several source systems or company files;
- unreconciled financials;
- poor inventory accuracy;
- many years of detailed history;
- complex multi-entity operations;
- custom integrations;
- extensive custom development;
- unclear requirements;
- compressed timeline;
- limited internal availability.
The cheapest proposal is not always the lowest-cost migration. An incomplete project can create expensive corrective work after go-live.
QuickBooks to Acumatica Migration Timeline
Migration duration depends on scope.
A basic financial migration with clean data and limited integration requirements can be completed much faster than a multi-entity transformation involving distribution, manufacturing, eCommerce, historical transactions, and several custom integrations.
The timeline normally includes:
- discovery and scope definition;
- Acumatica configuration;
- data cleansing and mapping;
- test migration;
- integration configuration or development;
- reporting;
- testing;
- training;
- final migration;
- go-live stabilization.
Factors That Shorten the Timeline
- clean data;
- clear process ownership;
- standard requirements;
- existing connectors;
- available decision-makers;
- limited historical migration;
- phased implementation.
Factors That Extend the Timeline
- multiple entities;
- complex data;
- full transaction history;
- custom development;
- many integrations;
- manufacturing or construction complexity;
- delayed approvals;
- insufficient testing resources;
- changing project scope.
A responsible implementation partner should provide milestones and dependencies rather than promising one universal duration.
Common QuickBooks to Acumatica Migration Mistakes
Mistake 1: Migrating Dirty Data
Importing duplicates, obsolete items, incorrect addresses, and unreconciled balances creates immediate distrust in the new ERP.
Mistake 2: Recreating QuickBooks Limitations
The company should not copy every old account, class, spreadsheet, and workaround into Acumatica.
The new system should support the future operating model.
Mistake 3: Skipping a Full Test Migration
Sample imports are useful, but the company should complete at least one realistic migration rehearsal with reconciliation before cutover.
Mistake 4: Migrating Too Much History Without a Business Reason
Full historical detail can increase cost and risk without creating equal value.
Mistake 5: Ignoring Integrations Until the End
Integrations influence customers, items, warehouses, taxes, payments, order types, and posting logic. They must be part of the initial architecture.
Mistake 6: Underestimating Inventory
Inventory migration requires agreement between quantities, values, warehouses, units, lots, serials, and the general ledger.
Mistake 7: Insufficient User Involvement
Users should participate in discovery, testing, training, and cutover approval.
Mistake 8: Rushing Financial Reconciliation
The trial balance alone is not enough. AR, AP, inventory, cash, projects, and open documents must also be validated.
Mistake 9: No Cutover or Rollback Plan
The company needs defined transaction freeze timing, backups, responsibilities, validation steps, and contingency decisions.
Mistake 10: No Post-Go-Live Support Plan
Users and integrations need active support during the first production cycles.
Industry-Specific QuickBooks to Acumatica Migration Considerations
Acumatica vs QuickBooks for Distribution
Distribution businesses often outgrow QuickBooks because inventory, purchasing, sales orders, warehouses, fulfillment, eCommerce, and financials are spread across several tools.
A distribution migration may include:
- inventory items and classes;
- multiple warehouses and locations;
- sales and purchase orders;
- customer-specific pricing;
- vendor relationships;
- replenishment rules;
- shipping integrations;
- EDI;
- returns;
- margin and inventory reporting.
The Acumatica target design should establish one source of truth for order-to-cash, procure-to-pay, inventory, and warehouse workflows.
Acumatica vs QuickBooks for Manufacturing
QuickBooks Enterprise can support manufacturing and wholesale scenarios, but growing manufacturers may require a more connected production environment.
An Acumatica manufacturing migration may involve:
- items and units of measure;
- bills of material;
- routing;
- work centers;
- production orders;
- material requirements planning;
- work in process;
- labor and overhead;
- job costing;
- engineering changes;
- shop-floor data;
- production and financial reconciliation.
Manufacturing data usually requires design work beyond direct QuickBooks field mapping.
Acumatica vs QuickBooks for Construction
Construction companies may need to connect accounting with projects, commitments, change orders, billing, retainage, field activity, payroll, and document workflows.
Migration considerations may include:
- projects and jobs;
- cost codes and account groups;
- budgets;
- commitments;
- subcontracts;
- change orders;
- project billing;
- open receivables and payables;
- retainage;
- field and office workflows;
- project history.
The company should decide whether active projects will be migrated in detail or introduced with approved opening positions.
Acumatica vs QuickBooks for eCommerce
An eCommerce business may use QuickBooks primarily for accounting while product, order, inventory, payment, warehouse, and fulfillment data are managed elsewhere.
The migration must connect:
- products and variants;
- SKUs;
- prices;
- customers;
- orders;
- taxes;
- payments;
- warehouses;
- inventory availability;
- shipments;
- tracking;
- returns;
- refunds;
- channel profitability.
BizTech’s proprietary commerce and marketplace connectors can reduce the need to develop each integration from the beginning.
Acumatica vs QuickBooks for Multi-Entity Businesses
A multi-entity migration may require:
- company and branch architecture;
- account and subaccount design;
- shared master data;
- intercompany transactions;
- currency handling;
- consolidated reporting;
- security separation;
- migration from several company files;
- entity-by-entity reconciliation.
This is often a transformation project rather than a simple accounting migration.
Why Work with BizTech for QuickBooks to Acumatica Migration?
BizTech is an Acumatica Gold Partner with experience in ERP implementation, data migration, customization, reporting, automation, integrations, training, testing, and post-go-live support.
Our migration approach combines functional and technical work.
BizTech can help with:
- QuickBooks environment assessment;
- business process discovery;
- Acumatica solution architecture;
- chart of accounts redesign;
- customer, vendor, and item migration;
- open AR and AP migration;
- inventory reconciliation;
- historical data strategy;
- custom Acumatica development;
- eCommerce and marketplace integrations;
- payment and warehouse integrations;
- reports and dashboards;
- user acceptance testing;
- role-based training;
- final cutover;
- ongoing support.
BizTech also develops proprietary Acumatica solutions. This matters because many companies moving from QuickBooks have already built a complex connected application environment.
Instead of replacing QuickBooks and leaving every other system disconnected, BizTech can help design Acumatica as the central ERP behind commerce, marketplaces, warehouses, payments, CRM, EDI, and custom platforms.
According to the BizTech website, the company is an Acumatica Gold Partner with more than 500 successful integrations and experience supporting businesses across more than 35 countries.
The practical advantage is one accountable partner for implementation and integration.
Why Partner Capability Matters
A migration partner should understand:
- accounting;
- operations;
- inventory;
- data transformation;
- Acumatica configuration;
- API integration;
- testing;
- training;
- go-live support.
A company that only understands data import may miss operational design.
A company that only understands accounting may miss integration architecture.
A company that only writes code may miss financial controls and business process requirements.
BizTech combines these disciplines in one Acumatica practice.
Final QuickBooks to Acumatica Migration Checklist
Before go-live, confirm the following.
Business and Scope
- Project objectives are documented.
- In-scope Acumatica applications are approved.
- Process owners are assigned.
- Required integrations are identified.
- Change requests are controlled.
Configuration
- Companies and branches are configured.
- Chart of accounts and subaccounts are approved.
- Customers, vendors, and item classes are configured.
- Warehouses and locations are configured.
- Order types and numbering sequences are configured.
- Taxes, terms, currencies, and payment methods are validated.
- Security roles are tested.
Data
- Duplicate records are resolved.
- Inactive records are reviewed.
- Opening balances are reconciled.
- AR and AP aging are reconciled.
- Inventory quantity and value are reconciled.
- Open sales and purchase orders are validated.
- Historical data strategy is approved.
- Final migration files are controlled.
Integrations
- Credentials are validated.
- Items, customers, warehouses, payments, taxes, and carriers are mapped.
- Orders are tested.
- Inventory synchronization is tested.
- Fulfillment and tracking are tested.
- Returns and refunds are tested.
- Error handling, retries, and logs are tested.
- Production schedules and webhooks are approved.
Reporting
- Financial statements are validated.
- Management dashboards are ready.
- Operational reports are approved.
- Security restrictions are tested.
- Legacy comparative reporting is addressed.
Users
- Users are created.
- Roles and permissions are tested.
- Role-based training is complete.
- Documentation is available.
- Support contacts and escalation paths are communicated.
Cutover
- Transaction freeze timing is approved.
- QuickBooks backups are complete.
- Final extraction responsibility is assigned.
- Final reconciliation steps are documented.
- Go-live approval criteria are defined.
- Rollback and contingency decisions are documented.
- Post-go-live support coverage is active.
Final Conclusion: Moving from QuickBooks to Acumatica
QuickBooks can support a business successfully for many years.
Moving away from it should not be treated as a criticism of the software or a mandatory milestone tied to revenue. The decision should be based on whether the current system environment still supports the company’s operational complexity, reporting needs, integrations, and growth strategy.
The strongest signs that a migration is needed are usually not accounting failures.
They are operational fragmentation, manual work, delayed visibility, disconnected inventory, complex consolidations, unreliable integrations, and an increasing dependence on spreadsheets and separate applications.
Acumatica provides a path from an accounting-centered environment to a connected cloud ERP platform.
A successful QuickBooks to Acumatica migration can give the business:
- one source of truth;
- connected financial and operational data;
- real-time inventory visibility;
- automated workflows;
- broader user access;
- industry-specific functionality;
- integrated eCommerce and marketplaces;
- stronger dashboards and reporting;
- open APIs and future flexibility;
- a scalable platform for growth.
But those benefits do not come from a basic data import.
They require business discovery, target architecture, data cleansing, configuration, integration, reconciliation, testing, training, cutover planning, and ongoing support.
As an Acumatica Gold Partner, BizTech helps businesses manage the complete transition from QuickBooks to Acumatica. Our team can migrate data, implement Acumatica applications, build custom functionality, connect external platforms, validate financials and inventory, train users, and support the new environment after go-live.
For companies searching for:
- QuickBooks to Acumatica Migration;
- Acumatica vs QuickBooks;
- QuickBooks Enterprise Alternative;
- QuickBooks Online to Acumatica Migration;
- QuickBooks Desktop to Acumatica Migration;
- QuickBooks to ERP Migration;
- Acumatica Data Migration Services;
- Acumatica Implementation Partner;
- Acumatica Gold Partner;
- BizTech Acumatica Migration;
the next step is a structured migration assessment.
QuickBooks provides the starting data.
Acumatica provides the connected ERP platform.
BizTech helps build the path between them.
FAQ: QuickBooks to Acumatica Migration
Can QuickBooks data be migrated to Acumatica?
Yes. Customers, vendors, inventory items, chart of accounts, opening balances, open AR and AP documents, sales and purchase orders, projects, and selected historical transactions can be migrated. Exact scope depends on the QuickBooks product, data quality, Acumatica configuration, and business requirements.
Can QuickBooks Online be migrated to Acumatica?
Yes. QuickBooks Online data can be exported, transformed, and imported into Acumatica. Connected applications and data stored outside QuickBooks Online must also be assessed.
Can QuickBooks Desktop Enterprise be migrated to Acumatica?
Yes. QuickBooks Enterprise can be migrated, including financials, customers, vendors, inventory, open transactions, and selected history. Advanced inventory, manufacturing, job costing, multi-company, and connected application workflows may require additional design.
Is Acumatica better than QuickBooks?
They serve different levels of complexity. QuickBooks is a strong accounting platform with capabilities that vary by edition. Acumatica is a complete cloud ERP platform designed to connect accounting with inventory, distribution, manufacturing, construction, projects, CRM, eCommerce, reporting, and automation.
When should a business move from QuickBooks to Acumatica?
A business should evaluate migration when disconnected systems, manual work, multiple entities, inventory complexity, slow reporting, integration failures, eCommerce growth, manufacturing, construction, or project requirements exceed the practical fit of the existing QuickBooks environment.
How long does a QuickBooks to Acumatica migration take?
Timeline depends on scope, data quality, entities, history, modules, integrations, customization, testing, and user availability. A basic financial migration can be much shorter than a multi-entity distribution, manufacturing, construction, or eCommerce transformation.
How much does QuickBooks to Acumatica migration cost?
Cost depends on Acumatica applications, implementation, data migration, integrations, customization, reporting, training, testing, and support. A discovery and data assessment are required for a reliable estimate.
Can historical QuickBooks transactions be migrated?
Yes, but the business should choose between full detailed migration, limited history, or opening balances with a legacy archive. Full history increases cost, transformation, testing, and reconciliation effort.
Can QuickBooks inventory be migrated to Acumatica?
Yes. Items, SKUs, units of measure, warehouses, quantities, costs, prices, vendors, and other inventory information can be migrated. Quantities and values should be reconciled before final cutover.
Can open QuickBooks invoices and bills be migrated?
Yes. Open customer invoices, vendor bills, credits, unapplied payments, deposits, due dates, and remaining balances can be imported and reconciled in Acumatica.
Should we keep QuickBooks after Acumatica goes live?
Some companies retain QuickBooks temporarily or as a historical archive. The decision depends on history migration, audit requirements, licensing, data retention, and whether users need direct access to legacy transactions.
Can Acumatica connect to our Shopify, WooCommerce, Amazon, or Magento store?
Yes. BizTech develops Acumatica connectors for Shopify, WooCommerce, Amazon FBA/FBM, Magento, and other commerce environments. These integrations can support orders, inventory, customers, products, payments, fulfillment, tracking, returns, and refunds.
Can BizTech migrate our company from QuickBooks to Acumatica?
Yes. BizTech is an Acumatica Gold Partner providing process discovery, Acumatica implementation, QuickBooks data migration, reconciliation, integrations, customization, reporting, training, cutover, and post-go-live support.
Why choose an Acumatica Gold Partner for migration?
A qualified Gold Partner combines Acumatica platform expertise with implementation, data migration, integration, testing, training, and long-term support. This reduces the risk of treating the project as a simple file conversion.
[/vc_column_text][/vc_column][/vc_row]
How Amazon FBA and FBM Data Flows into Acumatica ERP
August 6, 2026
How Shopify Data Flows into Acumatica ERP
August 5, 2026
How WooCommerce Data Flows into Acumatica ERP
August 4, 2026
How Shopify Data Flows into Acumatica ERP
How Shopify Data Flows into Acumatica ERP
Shopify data flows into Acumatica ERP as a controlled two-way exchange: the connector retrieves Shopify orders and imports them into Acumatica as Sales Orders, SO Invoices or AR Invoices, then sends results back out - fulfillment events, tracking numbers, inventory quantities, prices, products and customer data. Every leg of that flow is driven by settings you configure once on the Shopify Stores screen, so understanding the path a record takes is the difference between a Biz-Tech Services Shopify Acumatica integration that quietly works and one that silently drops orders.
This article walks that route end to end for the Biz-Tech Services Shopify Connector, following the direction records actually travel: credentials, inbound orders, the customer and payment and tax decisions attached to them, outbound fulfillment and order export, item and inventory sync, and errors. It names the real screens, tabs, buttons, checkboxes and fields your team will click, because those are what you check when you want to know what the integration did.
What the Shopify Connector for Acumatica Does
The Biz-Tech Services Shopify Connector is an integration between Shopify, an eCommerce platform, and Acumatica, an enterprise resource planning (ERP) system. It is delivered as an Acumatica customization project, published through the Customization Projects screen (SM204505), and requires a license of type PCSR, PERP or SAAS. Once published, it adds configuration, processing and inquiry screens that handle order sync, inventory management, product information sync, customer data sync, and the posting of sales data into Acumatica.
The connector talks to Shopify through its Application Programming Interface, or API, using connection information stored on the Shopify Stores screen. The Biz-Tech Services Shopify Acumatica integration also requires default options and required values for the order import process, which is why the store record carries so many settings. Based on those settings it connects to the corresponding system, retrieves orders, and imports the selected orders into Acumatica. When a user confirms the shipments created from those imported orders, fulfillment events are generated in Shopify for each corresponding order.
The Shopify Data Flow at a Glance
Before drilling into any single screen, it helps to see the whole path a record travels between the two systems:
- Setup - the connector package is published on the Customization Projects screen (SM204505), then a store is created from the Shopify Stores screen using Add New Store, which opens the Shopify Credentials screen. Test Credentials confirms the connection through the API.
- Configuration - on the Shopify Stores screen you set Import Settings, Tax Options, Customer Information, Item Information, Payment Options, Cross-Reference Options, Export Item Mappings, Warehouse Details and Order Export Settings. These decide what the connector is allowed to create.
- Retrieval - the Import Shopify Orders screen pulls orders with Get Orders. Only orders in Fulfilled, Unfulfilled or Partially Fulfilled status appear, filtered by Begin Order Date and afterwards by Last Imported Order Date.
- Staging - each retrieved order is written to the Shopify Orders screen, which holds its initial state - Order ID, Status, Payment Method, Ship Via, Document Details and Addresses - before it becomes an Acumatica document.
- Import - Import or Import All turns the staged order into the document type chosen in Import Shopify Orders to: a Sales Order, an SO Invoice or an AR Invoice, with the customer, items, payment and tax treatment your settings allow.
- Outbound fulfillment - when the shipment created from the imported order is confirmed, and after Prepare Invoice, the connector generates the Shopify fulfillment event and sends the tracking number back, updating the order status.
- Master data sync - separate processing screens push items, images, quantities, sales prices, template and matrix items, customers, contacts and locations, manually or on a scheduler.
- Exceptions - refunded orders come in through Import Shopify Refunded Orders, and export errors are logged with messages shown in the export log or notification center.
Setting Up the Connection: Shopify Credentials and Shopify Stores
Nothing flows until the store record exists, and these settings matter more than any other step: almost every downstream behavior - whether a customer is created, whether an item is created, whether a payment is attached - is a checkbox here rather than a decision made at import time.
How do you install the Shopify Connector in Acumatica?
The Biz-Tech Services Shopify Acumatica connector ships as a deployment package you import on the Customization Projects screen (SM204505), the same screen used to add, validate, publish, unpublish, export or delete any Acumatica customization project. On import, the platform uploads the package, creates the corresponding customization project and saves it in the database; publishing that project is what makes the Biz-Tech Services Shopify Acumatica integrator screens appear.
Where do Shopify credentials live?
Open the Shopify Stores screen and click Add New Store. You are redirected to the Shopify Credentials screen, where you complete the setup that integrates Acumatica with Shopify. Two actions govern the connection afterwards: Test Credentials, which tests the connection to the Shopify store through the API using the information on the Connection Settings tab, and Edit Credentials, which allows changes to the stored credentials. If Test Credentials fails, nothing downstream will work, so check it first whenever data stops moving.
The store-level fields that steer the whole flow
The header of the Shopify Stores screen carries the switches that determine which directions are even active:
- Store Code - a Lookup field indicating the corresponding Shopify store. It is required on the processing screens, so it ties every run to a specific storefront.
- Default Store - when selected, the default store automatically appears when you open the processing and Store screens and the Store Code field. Useful when you run one storefront and do not want users choosing the wrong one.
- Use B2B - allows customers to sync business-to-business, or B2B, data to Shopify. When unselected, the connector exports an ordinary customer instead.
- Use Webhook - enables the webhook logic to function, which is what lets Shopify events trigger Acumatica processing without a manual click.
- Export Order - activates the logic for exporting orders from Acumatica to Shopify, and makes the Order Export Settings tab appear.
Inbound: How Shopify Orders Become Acumatica Documents
The inbound leg is the heart of the Biz-Tech Services Shopify Acumatica integration. A shopper checks out, the connector retrieves the order, and Acumatica creates a document from it. What that document is, which orders qualify, and how much of the payload survives the trip are all governed by the Import Settings tab.
What document does a Shopify order become in Acumatica?
The Import Shopify Orders to field specifies the document type: Shopify orders can be imported as Sales Orders, Sales Order Invoices (SO Invoice), or Accounts Receivable Invoices (AR Invoice). Order Type represents the default type of orders created by the Biz-Tech Services Shopify Acumatica integration, and Branch determines where the order lands, using the branch values already set up on the store. Choose deliberately: a business that picks, packs and ships needs Sales Orders so shipments and fulfillment events can follow, while a business that only needs revenue recorded may be better served by an invoice.
Which Shopify orders are eligible for import?
Two filters decide what the Biz-Tech Services Shopify Acumatica connector will even look at. Fulfillment Status of Orders reflects the status of the corresponding order that will be imported. Under Order Status you will find the financial statuses; the corresponding checkbox must be selected for an order to be retrieved and imported. If a financial status is left unchecked, orders in that status simply will not appear - the most common reason an order seems to be missing.
Dates form the second filter. Begin Order Date is the date from which the first order should be imported. Last Imported Order Date shows when the last order was imported; for other invoice import processes it counts the date related to the last invoice date, and Last Refunded Order Date and Last Imported Company Date are the equivalents for refunds and companies. Retrieval begins from Begin Order Date only while Last Imported Order Date is not later than it; after that, orders are fetched from that watermark. These fields tell you where the connector believes it left off.
Import behavior options on the store record
Further checkboxes shape how much information travels with each order and how much API traffic the connector generates:
- Send Email Notifications for Errors - opens a field for an email address, and the connector notifies you of Order IDs that hit errors during retrieval. Turn this on if nobody watches the processing screen all day.
- Save Order Properties in Document Notes - retrieves order properties into document notes while fetching, preserving detail that has no dedicated Acumatica field.
- Skip Fulfillment - when selected, no API request is sent during Prepare Invoice and the order status is not updated. This deliberately breaks the outbound fulfillment leg, so leave it clear if you expect Shopify to reflect shipments.
- Refresh Order When Import Orders - when selected, the connector requests fresh data during import; when unselected it imports without updating anything. Selecting it costs extra API calls but guarantees the current version of the order.
Retrieving and importing Shopify orders
The Import Shopify Orders screen is where the inbound flow executes. Get Orders retrieves orders from Shopify, and a timer indicates elapsed time until the process completes. The page only shows orders with the statuses Fulfilled, Unfulfilled or Partially Fulfilled in the shop. Import then handles selected orders and Import All imports every order in the grid; if an error occurs, the message is displayed on screen with information about the system error. The screen also supports a schedule for getting and importing orders, so the cycle can run unattended.
What the Shopify Orders screen shows you
Each retrieved order carries a hyperlink; clicking the order number navigates to the corresponding Shopify Orders screen, which presents the initial situation of the order as it arrived - the best place to compare what came in against what Acumatica created. It has three tabs: Document Details, with information about the items; Addresses, with the customer address; and the Order ID field, which displays the Shopify order ID and order number.
The rest of the screen carries the linking fields. Status displays the order status in Acumatica, while Payment Method and Ship Via display the methods used. Sales Order Number shows the sales order created if the order was imported, and Invoice Number the invoice number if it was invoiced - so an empty Sales Order Number signals that the order was staged but never converted. Refresh Order updates the status, which matters because it reflects the initial state on import and does not change on its own if the order is later fulfilled in Shopify. Import Order fetches an order by its ID, after which it appears on the Import Shopify Orders screen ready to be imported - the manual path for a single urgent order. This screen is also where you read the raw payment method and Ship Via values when creating Cross-Reference mappings.
Automating the inbound flow with webhooks
Webhooks let Shopify events drive Acumatica instead of waiting for a scheduled run. When Use Webhook for Shopify Order Process Automation, Use Webhook for Shopify Fulfillment Process Automation and Use Webhook for Shopify Refund Process Automation are selected, the connector generates new Order, Fulfillment and Refund processes in the Shopify system. With order process automation on, any order created online is automatically imported into Acumatica on the Sales Orders screen, and the Webhook Order checkbox is then selected on the Shopify Orders screen - a quick way to tell an automated import from a manual one.
To create the mapping, go to the Webhooks screen, fill in the Webhook name and Implementation class, and click Save. A Webhook Uniform Resource Locator, or URL, is generated; that URL must be added to the URL field of the newly created webhook in the Shopify system. Until it is registered there, the Acumatica half has nothing to listen to.
Customers, Payments and Taxes on Imported Shopify Orders
An order is never just lines and totals. Each imported order drags a customer, a payment and a tax treatment behind it, and you control each on the Shopify Stores screen.
How does the connector decide which Acumatica customer to use?
When Import Customer is selected, the Biz-Tech Services Shopify Acumatica integration imports the customer information from Shopify into a new customer record in Acumatica. If it is not selected, orders are imported with the default customer instead - every order lands on one house account. Two checkboxes control addresses: Override Ship Address Information from Shopify Order imports the address the order will ship to, and Override Bill Address Information from Shopify Order the address of the party who will pay the bill. If the corresponding numbering sequence is absent, an error message is displayed, so customer numbering must exist first.
Cross-Reference: translating Shopify values into Acumatica values
The two platforms rarely use the same words for the same thing, and the Cross-Reference tab reconciles them. Cross-Reference Options on the Import Settings tab select the entities to be matched during the transition, and only the checked entities appear in the drop-down on the Cross-Reference tab. Selecting them makes the Ship Via field appear, letting you map the Shopify value to the Acumatica Ship Via value.
Customer assignment works the same way. If Use Tags to Import Customer is selected and the type Code is chosen, you set up the Shopify tags and Acumatica customer (AcctCD) values in the Shopify Value and Acumatica Value fields on the Cross-Reference tab. During import, orders carrying a mapped tag get that customer. If Use def. class if tag is not found is unselected, a new customer is created taking the customer class from the Cross-Reference tab. The same logic works for items.
How are Shopify payments imported?
Payment Options decide whether money travels with the order:
- Skip Shopify Payment - the order is imported from Shopify without payment.
- Import Captured CC Tran. as Payment - must be selected for an order that has a payment in Shopify to be imported with that payment. Otherwise the order arrives with none, whatever was collected at checkout.
- Payment Method - the method set on the payment during the order import process.
- Payment Type - Payment and Prepayment are the types a user can select during import.
- Release Payment During Order Import - the payment is imported already released, removing a manual step but also the chance to review it first.
Tax Options
Tax Options set how imported orders are taxed in Acumatica. Customer Tax Zone is the combined tax of effective taxes for a zone, defined according to the locations of the vendors or customers, and Tax ID is the customer tax identifier. Taxable Category creates or edits the tax categories applied to products, and Default Non-Taxable Category sets up an exempt category for non-taxable items and displays them on sales order lines. Because Shopify calculates tax at checkout, these fields keep the Acumatica side of the same order consistent with your tax configuration.
Point of Sale, discount and freight handling
Point of Sale, or POS, orders are placed at the point of sale, often in retail or hospitality. Use POS System enables their importation, POS Customer sets a default customer for them, and Default POS Item sets the default item for that process. Separately, Include Item Discount in Price includes the item discount amount in the order price rather than carrying it separately.
What happens to items that do not exist in Acumatica?
When Import Item is selected, the system may create a new item if it does not already exist in Acumatica during the sync and order import process, and options for imported item type, item class, unit of measure (UOM) and Warehouse ID appear to define the defaults. When Import Item is not selected, new item importation sets the default value of Replace Missing Products as the item name and takes the warehouse from Warehouse ID - so orders still import, but against a placeholder item.
Three functions become available with Import Item on. Use Numbering Sequence for SKU Generation generates a Stock Keeping Unit (SKU) number according to the numbering sequence setup when the system does not find one. Populate Items in Inventory Details adds the item into Inventory Details while importing. Save Item Properties in Line Notes syncs the order with line and header notes in Acumatica.
Outbound: Fulfillment, Refunds and Sales Order Export to Shopify
Once an order lives in Acumatica, the flow reverses. Shipments, invoices, refunds and even orders that started life in Acumatica all have a path back to the storefront.
When does Acumatica send fulfillment back to Shopify?
When a user confirms the shipments created from imported orders, fulfillment events are generated in Shopify for each corresponding order, and after the Prepare Invoice action the tracking number is sent and the Sales Order status is updated accordingly. Skip Fulfillment overrides this: with it selected, no API request goes out during Prepare Invoice and the order status is not updated. One detail on the way in: after the order import process, the Ship Via value appears in the Delivery Settings field on the Shipping tab of the Sales Orders screen.
How are Shopify refunds handled in Acumatica?
The Import Shopify Refunded Orders screen imports refunded orders into Acumatica. Press Get Orders to load them - a timer indicates elapsed time - and they are then displayed on the Shopify Refund screen. What happens next depends on how far the original order had progressed, which is why the same refund can produce very different documents:
- Case 1 - the order is a Sales Order with no fulfillments yet. If it consists of a single item, pressing Process generates a Payment with the Customer Refund type, attaches it to the Payments tab, sets the refunded amount and closes the order. The status changes to Canceled and all lines are deleted.
- Case 2 - a shipment was created but not confirmed. Process finds the shipment, deletes it, then proceeds as in Case 1.
- Case 3 - the shipment has been confirmed. Process creates a Credit Memo and attaches a reference number with the Customer Refund type to the Applications.
- Case 4 - the invoice is prepared but not released. The system creates a Credit Memo and attaches a reference number with the Customer Refund type to the Applications.
- Case 5 - the invoice is released. The system reverses the invoice.
How do you export Acumatica Sales Orders to Shopify?
Sales Orders created in Acumatica can be exported to Shopify through a designated export process. If a line item does not exist in Shopify, the system automatically creates a new product there using the Acumatica details; if the customer does not exist, a new customer record is created from the order information. Fields such as order number, date, customer details, item descriptions, quantities and prices are mapped and transferred according to predefined field mappings, and the new products and customers carry key identifying details to match their Acumatica counterparts.
There are two ways to export: the Actions menu on the Sales Order, and the Export Sales Orders processing screen, which shows only Sales Orders with Open or On Hold status, allows export individually or in bulk, and supports scheduler setup. Once exported, an order disappears from the screen and reappears if any updates are made. Exported Sales Orders are not imported back into Acumatica, so this is a one-way publish rather than a round trip. Two further actions manage exported orders: Shopify Cancel Order updates the order status to Cancelled after prompting for a cancellation reason, and Delete Shopify Order removes the order from Shopify entirely.
Order Export Settings: what travels with an exported order
The Order Export Settings tab appears when Export Order is selected. It defines how data is handled on the way out and sets fallback behavior when customer or product records are missing in Shopify:
1. Customer Settings - Export Customer exports customer information from the order; when unchecked, a field appears to specify a default customer used for all exports. Update Shipping Address and Update Billing Address create or update the corresponding address if the customer already exists.
2. Product Settings - Create Product creates new product records in Shopify when an item from the Sales Order does not already exist. When unchecked, the default product under Replace Missing Products is used instead.
3. Default Export Options - Export Once Created means that after creating and saving the order in Acumatica it appears in Shopify automatically. Order Fulfillment Status defines the initial fulfillment status of the exported order, for example Unfulfilled.
4. Export Transactions - specifies the payment status, such as Paid or Authorized. On Shopify Plus, with this selected, creating a payment from the Sales Order Payments tab or the Payments and Applications screen and saving it updates the payment status.
5. Export Tax Details, Export Discount and Export Freight - include the order tax information, discount details and freight data respectively.
6. Status Settings and Type Settings - define which Sales Order statuses (for example On Hold, Open) and Order Types (for example SO - Sales Order) are eligible, which also controls what appears on the Export Sales Orders screen.
After the order is placed, the customer receives notifications related to it, for example order cancellation or export notifications - so these settings have a customer-facing effect, not just an internal one.
Item and Inventory Sync Between Acumatica and Shopify
Product and inventory data is the third major flow, running mostly from Acumatica out to Shopify. It is also the flow most often blocked by an unchecked box, because a switchboard on the store record decides which fields the processing screens may touch.
Export Item Mappings: the master switchboard
The Export Item Mappings tab synchronizes product-related fields with Shopify and syncs the values of the item fields that are selected; fields that do not need updating can have their checkboxes cleared. This setting most often explains a sync that ran successfully but changed nothing: for all processing screens, if the required fields are not selected for creating or updating, the corresponding data - price, description, weight - will not be updated. Two related behaviors: the image checkbox applies to stock items and store export processes but does not influence the image processing screen, and if Track Quantity is clear in both systems an error message should appear during syncing, while if it is clear in Shopify only, the sync updates the quantity and selects that checkbox automatically.
The Shopify Inventory tab
On the Shopify Inventory tab you can load all Acumatica and Shopify items and then sync, publish or unpublish them. Load Acumatica Items retrieves all stock and non-stock items into the table, and Load Shopify Items does the same for the storefront catalog. Sync to Shopify exports Acumatica items outward; Sync from Shopify imports items in, taking the SKU and creating an Acumatica Inventory ID from it. Purge clears the table, and Get Item by ID retrieves a single item. The list can be exported and imported as an Excel document, and item sync, publish and unpublish can also be run from the Stock Items screen.
One asymmetry matters when planning your catalog: the Biz-Tech Services Shopify Acumatica connector does not support the mapping function during the Acumatica item export process, though on the import side you can map Shopify and Acumatica items to each other. When exporting an inventory item outward, the Biz-Tech Services Shopify Acumatica integration sets the item Inventory CD as the SKU, the identifier that keeps the catalogs aligned afterwards.
Inventory Mapping and Shopify metafields
The Inventory Mapping tab organizes the mapping between Acumatica attributes, item currency settings, user-defined fields and Shopify fields, and exports or updates metafields at the product or variant level. Get Metafields retrieves all existing metafields so you can organize the field mapping. Checkboxes specify whether each mapping is used for import or export. Acumatica Property should be set to the Acumatica item category and Shopify Property to the corresponding item category, and the relevant checkbox must be selected before importing or exporting mapped values.
Warehouse Details and quantity export
Warehouse Details is where Acumatica warehouses meet Shopify locations. Load Shopify Locations retrieves them all and lets you map them to warehouses; after the export from Export Shopify Inventory Quantities, the Biz-Tech Services Shopify Acumatica connector updates the quantity in the corresponding location. If several warehouses are selected, the exported quantity is the sum across them, and the drop-down value - On Hand, Available, or Available for Shipment - decides which figure syncs. This is a business decision: On Hand can oversell against allocated stock, while Available for Shipment is the most conservative.
On the Export Shopify Inventory Quantities screen itself, choose the required items beforehand on the Shopify Inventory tab of the Shopify Stores screen by checking the checkboxes and pressing Save. The screen displays the sum of item quantities according to the chosen warehouses and supports a schedule to avoid manual processing. It is possible to update the quantity even if Track Quantity is not selected for that item.
Exporting item data, images and prices
Dedicated processing screens carry specific slices of item data to Shopify:
- Export Shopify Inventory Items - synchronizes item price, description and weight. Load items into the store first, then select items and press Sync, or Sync All for everything displayed. This only works if the matching checkboxes are selected on Export Item Mappings.
- Export Shopify Product Images - enabled when the Product Image checkbox is selected on Export Item Mappings. Fill in Store Code, select the items, and press Sync or Sync All. If the checkbox is clear the image is not synced, and punctuation marks in the data will duplicate the image.
- Export Shopify Inventory Quantities - syncs quantities per mapped location, with scheduler support.
- Export Shopify Item Sales Prices - exports sales price lists as Shopify B2B catalogs, covered below.
Two behaviors apply across these screens. If the system does not find some items in the store during synchronization, it creates them automatically. And the Is Shopify Item checkbox is checked only for items that came from Shopify and were generated by the connector - a reliable way to distinguish connector-created items from ones your team keyed in.
How do Acumatica sales prices reach Shopify?
The Biz-Tech Services Shopify Acumatica integrator exports sales price lists from Acumatica to your store by leveraging Shopify B2B functionality, supporting customer price classes and individual customers including volume pricing and quantity rules, and synchronizing them as catalogs. Products, customers and customer locations must already be synced, and the customer or location must have a Customer Price Class assigned. What gets exported comes from the Sales Prices (AR202000) screen: prices are tied to a Customer Price Class or a Customer through the Price Code, and volume rules use Break Quantities. Define a Break Quantity greater than 1 to enforce minimum purchase quantities - if only 0 or 1 is defined, no quantity rule is exported.
A catalog is created for each unique combination of Customer Price Class and Currency, named CustomerPriceClassID-CurrencyCode, for example Wholesale-USD, with fixed pricing applied to all products within it. To run the export: assign a Price Class to the customer, confirm the customer and locations are synced, navigate to Export Shopify Sales Prices (BZ501005), select the records configured in Sales Prices (AR202000), and click Process or Process All. The system then creates or updates catalogs, adds prices including quantity breaks, and assigns customers or locations to the correct catalog. If the Price Type is Customer Price Class, the screen uses existing Shopify companies and adds them to the matching catalog.
Template items and matrix items
A Template Item is a base product used to create multiple variations, called Matrix Items. It defines general attributes but is not a sellable product itself - for example a T-Shirt template with Size and Color. Matrix Items are child products generated from a template; each is a unique combination of attributes, stocked, priced and sold separately, such as Red Small with SKU TS-RED-S. The Export Shopify Template Items process syncs template and matrix items separately or together, and after syncing the template item the Shopify Template ID is displayed on the Shopify Product tab.
To sync matrix items, click Sync Matrix Items, go to the Matrix Items tab, select the desired items, and click Include Item in Sync; they then appear on the Shopify Details tab, confirming they are in the store and ready to sync. Sync All Matrix Items syncs every matrix item along with the template product. On the Shopify Product tab, the Shopify Product Data field becomes available once the template item has been synced, and selecting its checkbox displays extra fields such as Custom URL, Meta Description and Page Title. The same logic applies to stock items: with the sync checkboxes selected the connector syncs items as template items with their matrix items, and with them clear it exports ordinary, individual products.
Shopify Collections
The Shopify Collections tab retrieves all collections and displays them in Acumatica when you press Get Collections. Purge All Collections clears them when you want to reload from scratch.
Customer and Company Sync Between Acumatica and Shopify
Customer data flows in both directions, and for B2B storefronts Acumatica is the authoritative side. For bidirectional synchronization with Shopify Plus B2B you must enable Use B2B in the store settings, which ensures Shopify correctly handles company profiles, multiple contacts per company, custom price lists, and customer and contact locations. Each B2B customer may have multiple users, added under the company. To push data outward, create a customer in Shopify with or without a contact, then press Sync Customer from the three-dot menu; Acumatica then updates Shopify with customer and contact data. Acumatica is the source of truth for customer details, so pressing Sync Customer assures the store gets the latest. You can also create and sync a password for a contact account through the Shopify Contact Password field.
The identifiers that link the systems live in specific places: the B2B customer ID appears on the Shopify Customers tab for customers linked to a B2B company; contact IDs are on the Contacts tab of the Customers screen and on the Contacts screen; and Location ID is stored on the Info tab of the Shopify Locations screen, ensuring the correct location is assigned and synced.
Four screens carry the customer flow. Import Shopify Companies imports company data into Acumatica; a company disappears from the screen once imported, indicating success, and filtering is based on the updated date field so only recently updated customers are retrieved. Export Shopify Companies exports customer, contact and location data in batches for bulk updates, and after a successful sync the customer disappears, reappearing only if changes occur. Export Shopify Customers processes customers on the scheduler, automatically or manually. The Shopify Companies screen allows manual import using Get Company by ID and Create Customer, which imports the company as an Acumatica customer along with its contacts and locations.
How the Shopify Connector Reports Errors
Errors surface in three places. On the Import Shopify Orders screen, an error during import is displayed on screen with information about the system error. For Sales Order export, errors such as invalid data or missing required fields are logged, with messages displayed in the export log or notification center. For unattended runs, Send Email Notifications for Errors emails the Order IDs that hit errors during retrieval. Two configuration problems have their own messages: an absent numbering sequence when a customer is being created, and Track Quantity not selected in both systems during item syncing.
Where to Monitor Shopify Results in Acumatica
Once the flow is running, most questions come down to whether a record made it and where it stopped. These are the exact fields, screens and buttons to check, roughly in the order a record travels:
- Shopify Stores screen, Test Credentials - confirms the connection to the store through the API. If this fails, nothing downstream will run.
- Shopify Stores screen, Last Imported Order Date - shows when the last order was imported and where the next retrieval starts; compare it against Begin Order Date. Last Refunded Order Date and Last Imported Company Date are the equivalents for refunds and companies.
- Import Shopify Orders screen - lists retrieved Shopify orders in Fulfilled, Unfulfilled or Partially Fulfilled status waiting to be imported, and displays the error message on screen when an import fails.
- Shopify Orders screen, Status - the order status as it was on import; use Refresh Order to update it against the current Shopify state.
- Shopify Orders screen, Sales Order Number and Invoice Number - the sales order created if the order was imported, and the invoice number if it was invoiced. Empty values mean the order was staged but never converted.
- Shopify Orders screen, Webhook Order checkbox - selected automatically after a webhook-driven import, distinguishing automated imports from manual ones.
- Sales Orders screen, Shipping tab, Delivery Settings - carries the Ship Via value that arrived with the order after import.
- Sales Orders screen, Shopify Order ID and store name - displayed after a Sales Order is exported, confirming the order now exists in Shopify.
- Sales Orders screen, Order is Synced and Exported checkboxes - selected automatically after export. If the order is updated afterward, Order is Synced clears and the order reappears on the Export Sales Orders screen; Mark/Unmark as Synced sets it manually.
- Export Sales Orders processing screen - lists only Sales Orders in Open or On Hold status still awaiting export. An order that disappears was exported successfully; one that reappears has been edited since.
- Stock Items screen, Is Shopify Item checkbox and Shopify Product tab - Is Shopify Item is checked only for connector-generated items, and the tab shows the Shopify Template ID plus Export to Shopify, selected automatically when the product exists there.
- The export log or notification center - where errors from the Sales Order export process are recorded.
Shopify Acumatica Integration: Frequently Asked Questions
Why is a Shopify order not appearing in Acumatica?
Work down the filters in order. The Import Shopify Orders screen only lists orders with the statuses Fulfilled, Unfulfilled or Partially Fulfilled, so an order in another state never shows up. Next check the Order Status section on the Import Settings tab: the corresponding checkbox must be selected for an order to be retrieved. Finally check the dates - retrieval starts from Begin Order Date only while Last Imported Order Date is not later than it, and afterwards orders are fetched from that watermark, so an older order is skipped.
Why was a customer not created in Acumatica from a Shopify order?
The most likely cause is the Import Customer checkbox on the Shopify Stores screen. If it is not selected, orders are imported with the default customer instead of creating a new record. If it is selected and creation still fails, check numbering: an absent numbering sequence produces an error message. If you use tags, confirm the Use Tags to Import Customer setup on the Cross-Reference tab, because when Use def. class if tag is not found is clear, a new customer is created taking the customer class from that tab.
Why did an item price, description or weight not update in Shopify?
This is almost always the Export Item Mappings tab. For all processing screens, if the required fields are not selected for creating or updating, the corresponding data such as price, description or weight will not be updated. Select the appropriate checkboxes there before using the processing screens, then re-run Sync or Sync All on the Export Shopify Inventory Items screen.
Why is Acumatica not sending fulfillment back to Shopify?
Check the Skip Fulfillment checkbox on the Shopify Stores screen. When it is selected, no API request is sent during the Prepare Invoice action and the order status is not updated. With it clear, confirming the shipments created from imported orders generates Shopify fulfillment events, and the tracking number is sent after Prepare Invoice with the Sales Order status updated accordingly.
Can Shopify orders be imported as invoices instead of Sales Orders?
Yes. The Import Shopify Orders to field specifies the document type, and Shopify orders can be imported into Acumatica as Sales Orders, Sales Order Invoices (SO Invoice), or Accounts Receivable Invoices (AR Invoice). Order Type sets the default type created by the Biz-Tech Services Shopify Acumatica integrator, and Branch uses the branch values already set up on the store.
Does the Shopify Connector import payments with the order?
Only if you tell it to. Import Captured CC Tran. as Payment must be selected for an order that has a payment at checkout to be imported with that payment; otherwise it arrives without one, and Skip Shopify Payment does the opposite. Payment Method and Payment Type - Payment or Prepayment - set what is created, and Release Payment During Order Import causes the payment to arrive already released.
How do I run the Shopify integration automatically instead of clicking buttons?
There are two mechanisms. Several processing screens support scheduler setup, including Import Shopify Orders, Export Shopify Inventory Quantities, Export Sales Orders and Export Shopify Customers. Separately, webhooks work in real time: with Use Webhook enabled and Use Webhook for Shopify Order Process Automation selected, any order created in Shopify is automatically imported into Acumatica on the Sales Orders screen, with equivalent options for fulfillment and refunds.
What happens in Acumatica when a Shopify order is refunded?
It depends on how far the order had progressed. If it is a Sales Order with no fulfillments, processing the refund creates a Payment with the Customer Refund type, sets the refunded amount, closes the order, changes the status to Canceled and deletes all lines. If a shipment was created but not confirmed, it is deleted first and the same path follows. If the shipment was confirmed, or the invoice was prepared but not released, the system creates a Credit Memo with a Customer Refund reference in the Applications. If the invoice was already released, the system reverses it.
Work With the Biz-Tech Services Shopify Connector
The Shopify data flow into Acumatica ERP is a chain, and every link is a setting you control. Credentials and store configuration decide whether the Biz-Tech Services Shopify Acumatica connector can connect at all. Import Settings decide which orders qualify and what document they become. Customer Information, Payment Options, Tax Options and Item Information decide how much of the original order survives the trip. Export Item Mappings and the processing screens decide what your storefront sees of your catalog, inventory and prices, and Order Export Settings decides what happens to orders that start life in Acumatica. When you know which screen owns which decision, troubleshooting stops being guesswork.
If your business runs a Shopify storefront on top of Acumatica ERP and you want that data flow configured, monitored and running without manual intervention, the Biz-Tech Services team can help you set it up correctly the first time. Visit https://biz-techservices.com to learn more about our Acumatica expertise or to schedule a personalized demonstration of the Shopify Connector.
How DocVision Converts PDF Purchase Orders into Acumatica Sales Orders
How DocVision Converts PDF Purchase Orders into Acumatica Sales Orders
DocVision turns a customer's PDF purchase order into an Acumatica sales order without anyone retyping a line. That sounds simple, but the data flow behind it has a clear shape worth understanding: a PDF is imported and becomes a reusable template, the template maps every PDF field to an Acumatica field, cross-references resolve the customer and the items, a review screen shows in color whether the document is ready, and only then is the sales order generated. Knowing which stage a document has reached, and which field controls the next step, is what makes PDF automation dependable rather than unpredictable.
The Biz-Tech Services DocVision product is a PDF scan and import enhancement built natively for Acumatica ERP. Users upload PDF files such as purchase orders or shipping requests and generate the corresponding sales orders inside Acumatica, eliminating manual data entry. This article follows a PDF through the entire flow, from the initial setup and template creation to the generated sales order, and identifies the fields users should monitor at each point.
What DocVision Does in Acumatica
DocVision is an Acumatica ERP enhancement that automates the creation of sales orders from PDF documents. It reads an uploaded PDF, identifies the customer and ship-to information using pre-configured templates, maps the document's values to Acumatica fields, and generates a sales order from the result. Because parsing rules are defined per customer, the same system can handle many different document formats and structures, which matters when every customer sends purchase orders in their own layout.
Several characteristics shape how the product behaves in practice. It is built natively for Acumatica, so it runs without external dependencies and works within Acumatica's secure environment, respecting user permissions and audit trails. It reduces data entry mistakes by extracting information directly from the source document, and it standardizes incoming sales data regardless of the style of the originating document. For high-volume sales operations, that combination of speed and consistency is the point of the product.
The DocVision Data Flow at a Glance
Before looking at individual screens, here is the path a PDF travels to become a sales order:
- Azure setup establishes and tests the credentials that allow customer purchase order PDF files to be brought in and processed.
- On the PDF Import Settings screen, a PDF is imported and a template is created, defining the mapping between PDF values and Acumatica values.
- The system automatically populates PDF FieldName, PDF Value, and the Target Object and Source Field mappings, which can then be adjusted manually.
- Inventory and customer cross-references resolve the PDF's item and customer values to real Acumatica inventory IDs, customers, and locations.
- On the Import Documents screen, each document is reviewed, with green, red, and yellow indicating readiness, errors, and mapping warnings.
- Generate Sales Order creates the order, sets the Generated checkbox, and records the order number and order type against the document.
- The Import PDF Documents inquiry and the batch generation screen provide oversight across many documents at once.
Each field discussed below sits at one of those handoffs.
Stage One: Azure Setup and Testing Credentials
Setting up Azure in Acumatica allows the ERP system to run on Microsoft's cloud platform using services such as Azure SQL Database, Virtual Machines, and Storage. Beyond the general benefits of scalability, security, performance, backups, disaster recovery, and Single Sign-On through Azure Active Directory, this configuration is what supports importing customer purchase order PDF files so they can be processed and converted into sales orders within Acumatica.
One control on this screen deserves to be used before anything else is attempted. The Test Credentials button confirms that the setup credentials are configured correctly. Running it early is the cheapest way to separate a credential problem from a mapping problem later, and it should be the first checkpoint whenever documents stop arriving.
Stage Two: Building a PDF Template in PDF Import Settings
PDF Import Settings is where the intelligence of the product lives. Pressing the plus button opens a new workspace that allows a PDF file to be imported and a template created from it. Once the PDF is imported, the screen defines the mapping between PDF values and Acumatica values, and that mapping is what every future document of the same format will reuse.
Reading the automatic mappings
After a PDF is imported, the right side of the screen displays the file itself, with the ability to move to the next or previous page and to zoom in and out, so the source document can be read while mapping. The system automatically sets the PDF FieldName and PDF Value entries, and on the Import Mappings tab it also automatically sets the mappings between Target Object and Source Field values. From there it is possible to manually map all PDF fields to the corresponding Acumatica values, correcting or extending what was detected automatically.
Header versus detail mapping: the Target Object rule
One rule governs whether a mapped value lands on the order header or on an order line, and getting it wrong is a common early mistake. To map header fields of a sales order, select Sales Order and then Advanced in the Target Object. To map details on the Sales Order screen, select Sales Order, then Details, then Advanced. The presence or absence of Details in that path is the entire difference between a value appearing once on the order and appearing on each line.
The Active checkbox decides what actually gets written
During sales order generation, only the fields for which the Active checkbox is selected will be uploaded. This is the single most important field to check when a mapped value fails to appear on a generated order. The mapping can be entirely correct and still produce nothing if Active was never selected, which makes this checkbox the first place to look rather than the last.
Handling PDFs that have no purchase order number
Not every incoming document carries a purchase order number, and DocVision handles that case explicitly. Under the Description section there is a Dynamic PO Number field. If there is no purchase order number in the PDF file, this checkbox is automatically selected during the file import process and a warning is displayed reading that the document for the mapping does not have any number and asking you to select an alternative purchase order number.
After that warning appears, a Release PO Number field becomes available, which allows the values of the header to be mapped to existing values of the field. In other words, the system does not simply reject a document without a number; it asks you to nominate which header value should serve as the number instead.
Inventory and customer cross-references
Two cross-reference layers translate the PDF's vocabulary into Acumatica's. Enabling CrossRef for the Inventory ID field makes the Inventory Cross-Reference tab appear, where PDF items can be mapped manually to Acumatica inventory IDs, or where all items can be imported at once via Excel. The Excel route matters for onboarding a customer with a long catalog, since mapping item by item does not scale.
When Cross Reference is selected, the Customer Cross-Reference tab appears, allowing PDF customer values and locations to be mapped to Acumatica customers and locations. This is the mechanism behind the product's customer recognition: the template knows that a particular string in a particular position identifies a specific Acumatica customer and ship-to location.
Stage Three: Reviewing Documents on the Import Documents Screen
The Import Documents screen is the review and correction stage. It allows changes to be made to existing or previously imported documents, and it also enables documents to be imported directly from this screen. Selecting a document number displays the PDF already imported through PDF Import Settings along with all mappings for that document, and it retains the Template ID information, so you can always see which template produced a given result.
The green, red, and yellow color code
Three colors communicate document readiness at a glance, and teaching users to read them saves a great deal of investigation:
- Green indicates that everything is mapped correctly and the file is ready for generating a sales order.
- Red indicates that an item line hit an issue during the import process; the line turns red and an error message is displayed in the Error Message field.
- Yellow indicates a mapping problem, for example items that are not mapped correctly.
The distinction between red and yellow is worth stressing. Red points to a specific failure with a message attached, so the Error Message field tells you what happened. Yellow is a warning that the document is not yet ready, most often because item mapping is incomplete.
Resolving yellow warnings with Validate Items
Yellow warnings are addressed with the Validate Items button. It maps all PDF items to their Acumatica values and displays them on the Details tab, provided those items are already mapped in the Inventory Cross Reference on the PDF Import Settings screen. That proviso is the key to using it well: Validate Items applies existing cross-references, it does not invent them. If an item has never been cross-referenced, validation cannot resolve it and the cross-reference must be created first. The button can be used frequently when PDFs are imported from the same screen.
Stage Four: Generating the Sales Order
On the Documents tab, the Template ID, document number, Order Type, and Customer are displayed, which together confirm that the right template and the right customer were matched before anything is created. Once setup is complete, opening the three dots menu and selecting Generate Sales Order creates a sales order from all the mapped data.
Three results confirm success, and users should check all of them. The order number and order type are displayed against the document, the Generated checkbox is automatically selected, and the document number becomes visible on the Sales Order screen itself. That last item is the important one for traceability, because it means anyone looking at the resulting sales order can see which imported document produced it.
Batch Processing and the Import PDF Documents Inquiry
Two features exist for working across many documents rather than one at a time. A generic inquiry has been created where all document numbers, Template IDs, customer information, and document generation dates can be found, with hyperlinks on those fields that lead directly to the Import Document screen. This is the natural starting point for a daily review, since it answers what came in, under which template, for which customer, and when.
For processing volume, the Generating Sales Orders screen has been modified to allow orders to be imported in batches and sales orders generated from them. The Document Number field can be used to filter by document number and generate the corresponding sales order, which makes it practical to work through a queue of documents rather than opening each one individually.
Where to Monitor DocVision Results in Acumatica
When configuring templates, training users, or investigating a PDF that did not produce the expected order, these are the fields and screens that show what actually happened:
- The Active checkbox on each mapping, since only fields with it selected are uploaded during sales order generation.
- The Target Object path, where Sales Order then Advanced maps a header field and Sales Order then Details then Advanced maps a line field.
- The Dynamic PO Number checkbox and the Release PO Number field, which together handle documents that arrive without a purchase order number.
- The Inventory Cross-Reference tab, which resolves PDF items to Acumatica inventory IDs and can be loaded in bulk from Excel.
- The Customer Cross-Reference tab, which maps PDF customer values and locations to Acumatica customers and locations.
- The color of each line on the Import Documents screen, where green means ready, red means a line-level error, and yellow means a mapping warning.
- The Error Message field on any red line, which carries the specific reason the line failed.
- The Template ID retained against each document, which identifies which template produced the mapping.
- The Generated checkbox, order number, and order type on the Documents tab, which confirm the sales order was created.
- The document number displayed on the Sales Order screen, which links the finished order back to its source PDF.
- The Import PDF Documents generic inquiry, for document numbers, Template IDs, customer information, and generation dates across all documents.
DocVision for Acumatica: Frequently Asked Questions
What is DocVision for Acumatica?
DocVision is a Biz-Tech Services enhancement for Acumatica ERP that automates the creation of sales orders from PDF documents. Users upload PDFs such as purchase orders or shipping requests, and DocVision extracts the data using pre-configured per-customer templates and generates the corresponding sales order in Acumatica, removing the manual data entry step.
How does DocVision know which customer a PDF belongs to?
Through the Customer Cross-Reference tab, which appears when Cross Reference is selected. It maps PDF customer values and locations to Acumatica customers and locations, so the system can identify customer and ship-to information from each PDF using the pre-configured template. Because parsing rules are defined per customer, different customers can send completely different document layouts.
What do the green, red, and yellow colors mean on the Import Documents screen?
Green means everything is mapped correctly and the file is ready for sales order generation. Red means an item line encountered an issue during import, with the reason shown in the Error Message field. Yellow means a mapping problem, typically items that are not mapped correctly, which the Validate Items button can often resolve.
What happens if a PDF has no purchase order number?
The Dynamic PO Number checkbox under the Description section is automatically selected during import and a warning appears stating that the document for the mapping does not have any number and asking you to select an alternative. The Release PO Number field then becomes available, letting you map header values to existing values of the field so the document still receives a usable number.
Why is a mapped field missing from the generated sales order?
Check the Active checkbox on that mapping first. During sales order generation only fields with Active selected are uploaded, so a correct mapping with Active cleared produces nothing. If Active is set, verify the Target Object path, since header fields require Sales Order then Advanced while line fields require Sales Order then Details then Advanced.
How do you map PDF line items to Acumatica inventory IDs?
Enable CrossRef for the Inventory ID field, which makes the Inventory Cross-Reference tab appear. From there, PDF items can be mapped manually to Acumatica inventory IDs, or all items can be imported at once through Excel. Once those cross-references exist, the Validate Items button on the Import Documents screen will apply them and populate the Details tab.
Can DocVision generate sales orders in batches?
Yes. The Generating Sales Orders screen supports importing orders in batches and generating sales orders from them, and the Document Number field can be used to filter by document number and generate the corresponding order. The Import PDF Documents generic inquiry gives an overview of all documents, with hyperlinks back to the Import Document screen.
Work With the Biz-Tech Services DocVision Product
DocVision is straightforward once the flow is clear. Azure setup and tested credentials open the door, PDF Import Settings turns a sample document into a reusable per-customer template, the Active checkbox and the Target Object path decide what is written and where, inventory and customer cross-references translate the document into Acumatica's own identifiers, the Import Documents screen shows readiness in color, and Generate Sales Order completes the journey with the document number visible on the finished order. Teams that know which field governs each handoff can turn a stack of customer PDFs into accurate sales orders quickly and consistently.
If your business receives customer purchase orders as PDFs and wants them turned into Acumatica sales orders without manual re-keying, we are glad to help you scope, configure, and roll out DocVision. Visit https://biz-techservices.com to learn more about our Acumatica expertise or to schedule a personalized demonstration of the Biz-Tech Services DocVision product.
How WooCommerce Data Flows into Acumatica ERP
How WooCommerce Data Flows into Acumatica ERP
The WooCommerce Acumatica integration moves data in both directions, and that is the first thing to understand about it. Orders travel inbound from your store to become Acumatica sales orders, while items, quantities, prices, images, customers, and fulfillment events travel outbound from Acumatica back to WooCommerce. A single configuration screen governs almost all of it. Knowing which setting controls each handoff, and which screen shows the result, is what turns a large connector into a predictable one.
The Biz-Tech Services WooCommerce Connector links WooCommerce, the e-commerce platform, with Acumatica ERP. The integration retrieves orders from WooCommerce and imports the selected orders into Acumatica, and when a user confirms the shipments created from those imported orders, fulfillment events are generated in WooCommerce for each corresponding order. This article follows records through the full data flow in both directions and identifies the fields worth monitoring at every stage.
What the WooCommerce Connector for Acumatica Does
The WooCommerce Connector is an Acumatica ERP customization that synchronizes an online store with the back office. Inbound, it retrieves WooCommerce orders and creates Acumatica sales orders from them, optionally importing customers, addresses, payments, discounts, taxes, and shipping details along the way. Outbound, it exports items, inventory quantities, prices, sales prices, images, and product categories to WooCommerce, publishes and unpublishes products, exports customers, and reports shipment and invoice progress back to the store so order status stays current on both sides.
After the customization package is published, the WooCommerce workspace appears in the Acumatica menu along with its screens. Two of those screens matter more than the rest: WooCommerce Store Preferences manages the connection and the API setup, and WooCommerce Store manages the overall workflow and its configuration. Almost every behavior described in this article traces back to a setting on the second of those two screens.
The WooCommerce Data Flow at a Glance
Before looking at individual screens, here is the path records travel through the Biz-Tech Services Acumatica WooCommerce integration:
- Credentials are entered and validated on WooCommerce Store Preferences, which also auto-populates the Order Mappings tab.
- The WooCommerce Store screen defines operating mode, order settings, item settings, mappings, cross-references, warehouses, categories, and webhooks.
- Get Orders retrieves WooCommerce orders, which are routed to either the Import WooCommerce Orders screen or the WooCommerce Orders screen depending on their status.
- Import creates the Acumatica sales order, applying customer, payment, discount, tax, and shipping rules from the store configuration.
- Fulfillment runs Create Shipment, Confirm Shipment, Prepare Invoice, and Release, pushing shipment and invoice information back to WooCommerce.
- Export Item Processes push items, quantities, images, prices, and publication status outward, in batches of one hundred items per API request.
- Customer export, refund import, webhooks, and automation schedules run alongside the main order flow.
Each field discussed below sits at one of those handoffs.
Stage One: Credentials and the Two Setup Screens
Setup begins on the WooCommerce Store Preferences screen, where you enter the credentials generated on your WooCommerce website. Store Code is a lookup field indicating the corresponding WooCommerce store name, and Description holds a description of that store. The connection itself relies on the Consumer Key, Consumer Secret, and Base URL, which are the WooCommerce system credentials used during integration, together with the WordPress Login and WordPress Password fields, which hold the WordPress credentials required for authentication.
After entering the credentials, click Test Credentials. If the message confirming that credentials are valid appears, you can proceed to the WooCommerce Store screen. Do not skip this step, because it is the cheapest way to separate a connection problem from a configuration problem later.
Saving this screen does more than store credentials. During the save process, the Order Mappings setup is configured under the Order Mappings tab of the WooCommerce Store screen, and all required default fields are added automatically. That mapping determines how order synchronization is carried out, so a successful save is what makes order import possible at all.
Generating the WooCommerce API keys
The WooCommerce REST API works on a key system that controls access, and those keys are linked to WordPress users on your site. To generate them, go to WooCommerce, then Settings, then Advanced, then REST API, and choose Add Key. Add a description, select the user the key is being generated for, and select the level of access, which can be read access, write access, or read and write access. Selecting Generate API Key produces the Consumer Key and Consumer Secret used on the preferences screen. Choose the access level deliberately, since a read-only key will block every outbound process described later in this article.
Stage Two: The WooCommerce Store Screen Governs Everything
The WooCommerce Store screen is the main screen of the connector, and the configuration defined here determines how the Biz-Tech Services Acumatica WooCommerce connector functions. It controls order import, item import and creation, payment processing, customer management, shipping methods, warehouse mapping, and related settings. Proper configuration of this screen is what ensures accurate synchronization between the two systems.
The three switches that set operating mode
Near the Store Code at the top of the screen, three fields define the system's operating process in advance. When the Use B2B Store checkbox is selected, the system operates in business-to-business mode, synchronizing the customer's contact information and creating a corresponding user account in WooCommerce; when it is cleared, the Biz-Tech Services Acumatica WooCommerce integration handles standard retail workflows instead. The Use Refund Process option enables processing of WooCommerce refunded orders and reveals the Last Refunded Order Date field on the Order Settings tab. Use Webhook adds a Webhook Settings tab to the screen.
A Default Store checkbox in the header sets that store automatically in the Store Code field on the processing screens, which removes a repetitive selection step from daily work.
Two actions worth knowing
Edit Credentials redirects to the WooCommerce Store Preferences screen for editing. Update Synchronized Customers transfers WooCommerce customer information from the WooCommerce Info tab of the Customers screen to the Woo Customer Info tab. This second action is not optional housekeeping: customer synchronization is currently based on the Woo Customer Info tab, so after publishing a new package the existing data must be transferred using this action or customer matching will not work correctly.
The details section of the screen carries several tabs, including Order Settings, Item Settings, Item Mappings, Cross-Reference, Warehouse Details, Item Details, Product Categories, and Inventory Mapping, each configuring its corresponding process.
Inbound: How WooCommerce Orders Become Acumatica Sales Orders
The Order Settings tab configures order synchronization from WooCommerce to Acumatica. Import WooCommerce Orders To specifies the type of Acumatica document the orders become, with Sales Orders creating standard Acumatica sales orders. Order Type defines the default order type for all orders created by the Biz-Tech Services Acumatica WooCommerce integrator, and Warehouse ID specifies the default warehouse assigned to imported orders, which keeps inventory availability and stock management aligned with the right warehouse.
The date fields that control how much is imported
Begin Order Date sets a starting point to filter which WooCommerce orders are retrieved, so only orders created on or after that date are imported, enabling partial or incremental loading. Last Imported Order Date displays the date of the most recent order successfully imported, and the next import begins from that date so orders are neither skipped nor duplicated.
One detail deserves emphasis because it explains behavior that otherwise looks wrong. Orders are imported into Acumatica based on their updated date rather than their created date. An older order that was recently modified will therefore be picked up, which is intentional and keeps changes in sync.
Status filtering and which screen an order lands on
WooCommerce Status determines which orders are imported based on their status, such as Completed, Processing, or On Hold, and only orders matching a selected status are included. The corresponding order status checkbox must be selected for an order to be retrieved and imported at all, which is the first thing to check when expected orders never appear.
Retrieved orders are then routed to one of two screens according to status. Orders with working statuses, documented as on hold, partial shipped, processing, and pending, appear on the Import WooCommerce Orders screen, where the processing page shows partially shipped, on hold, pending, pending payment, and processing orders. Orders with canceled, failed, empty, and completed statuses appear on the WooCommerce Orders screen instead. Understanding this split prevents a great deal of confusion, because an order that is not on the import screen has usually not gone missing; it is simply in a status that routes it elsewhere.
Retrieving and importing
On the Import WooCommerce Orders screen, the Get Orders button retrieves orders from WooCommerce, with a timer showing elapsed time until the process completes. All orders for the selected period are retrieved and displayed at once. The Import button then imports the selected orders, while Import All imports everything displayed on the grid. A scheduler can also be configured on this screen to retrieve orders automatically.
Reading the WooCommerce Orders screen
Each retrieved order carries a hyperlink on its order number that navigates to the corresponding WooCommerce order screen. That screen presents the initial status of the order and organizes detail across several tabs: Document Details for the order's items, Addresses for the customer's address details, Import Fields for information relating to the order mappings configured in the store, and Refund Info, which becomes visible only if the order has been refunded.
The header fields are where users check results. Order ID displays the WooCommerce order ID and order number, Status shows the WooCommerce order status inside Acumatica, and Payment Method and Ship Via show how the order was paid and how it ships. Sales Order Number displays the resulting sales order once the order has been imported, and Invoice Number appears once it has been invoiced. Financial totals are carried in Total Lines Amount, Discount Total, Shipping Total, Total Tax, and Total, the last representing the final amount paid.
Two actions sit on this screen. Import Order retrieves an individual order from WooCommerce by selecting the store code and setting the order ID, which is useful for one-off recovery. Refresh Order updates the WooCommerce order status in Acumatica, which matters when an order is fulfilled in WooCommerce after it was imported.
One caveat about mappings belongs here. The Import Fields tab is populated based on the order mapping during the Get Order process and is then imported into Acumatica during the order import. Changes to the Order Mapping configuration do not affect orders that have already been retrieved. To adjust an already-retrieved order, users must edit it manually from the Import Fields tab before importing it.
Customer, Payment, Discount, and Tax Handling on Import
Customer information options
These options determine whether customer data from WooCommerce is imported and created in Acumatica. Import Customer brings customer information into a new Acumatica customer record. Override Ship Address Information from WooCommerce Order imports the address the order ships to, and Override Bill Address Information from WooCommerce Order imports the address of whoever pays the bill. Customer Class sets the default class applied to new customers created by the Biz-Tech Services Acumatica WooCommerce integration.
If Import Customer and both address options are left unselected, customer data is not imported and the order is created using the default customer information in Acumatica. A table under Customer Information also lets you determine the priority of WooCommerce fields when importing and exporting customers between the two systems.
Shipping and payment options
Shipping Options determine which shipping information is imported, and based on the configured setup the shipping total can be imported as either the Freight Price or the Premium Freight Price.
Payment Options determine whether payment information is imported. Selecting Skip WooCommerce Payment means imported orders carry no payment information and the order is created without recording one. Leaving it cleared reveals further configuration: Payment Method specifies the method assigned during import, such as credit card, PayPal, or bank transfer; Payment Type determines the payment type in Acumatica, such as prepayment, cash, or credit; and Release Payment during Order Import automatically releases the payment at import time so the financial transaction is processed immediately.
Payment authorization and capture
The division of labor between the two systems is worth explaining to finance teams before go-live. In WooCommerce, payments can be authorized at checkout, meaning the customer's card details are verified and funds are reserved by the gateway without being collected. Once the order synchronizes into Acumatica, the system does not attempt to authorize again. Instead it performs a post-authorization, recording the authorization already completed in WooCommerce and bringing it into Acumatica's accounts receivable so financial records stay consistent.
From there the payment can be captured directly in Acumatica when the order is ready to be fulfilled. The practical effect is that WooCommerce secures the funds at order creation while Acumatica collects them at the most appropriate point in your process. The Biz-Tech Services Acumatica WooCommerce connector supports Ebizcharge and Fortis as well as other credit card payment methods, and the corresponding payment method must also be set up in Acumatica for the card payment to process correctly.
Discounts and taxes
Discounts are handled two ways. Line-level discounts are calculated for each individual item, populating the Discount Amount and Discount Code fields in the Sales Orders document details table. Order-level discounts apply to the entire order and appear in the Discount section of the order instead.
Tax options ensure WooCommerce taxes are calculated and applied correctly in Acumatica and provide flexibility for external tax services. Customer Tax Zone is the combined tax of effective taxes for a zone, defined by vendor or customer location. Tax ID holds the customer's tax identifier, and Taxable Category creates or edits the tax categories applied to products. Is Freight Taxable in WooCommerce controls whether freight is taxed on the WooCommerce side, and Use External allows another tax engine such as Avalara to be used where the plugin is in place.
Other order settings worth knowing
Do Not Import WooCommerce Price makes the system ignore WooCommerce prices during import and use the corresponding Acumatica item prices instead; selecting it disables the Send Invoice Info during Release option. Save Properties in Order Notes causes the connector to retrieve notes along with the orders. Send Email Notification for Errors alerts users to failures during import, with notifications going to the email address entered on the Order Settings tab and sent during batch imports and process updates.
Cross-References and Warehouse Configuration
Cross-Reference options specify which entities should be matched between the two systems during synchronization, so that payments, countries, or ship via values in WooCommerce correspond correctly to their Acumatica equivalents and duplicate or mismatched records are avoided. Only entities checked in Cross-Reference Options appear in the dropdown on the Cross-Reference tab, where the actual mappings are created. Get Shipping Methods loads WooCommerce shipping methods so they can be mapped against Acumatica Ship Via values. After order import, the mapped Ship Via value should be visible in the Delivery Settings field on the Shipping tab of the sales order.
The Warehouse Details tab is where you add the warehouses whose inventory quantities need to synchronize with WooCommerce. The system calculates the total quantity across all selected warehouses for each item and displays that combined figure on the processing screen for export, so the store reflects stock across every relevant warehouse. A dropdown determines which quantity is used, with On Hand, Available, and Available for Shipment as the options. This choice directly controls what your store believes it can sell, so it should be made deliberately.
Outbound: Fulfillment Events Back to WooCommerce
When a WooCommerce order is associated with an Acumatica sales order, fulfillment runs in four steps. Click Create Shipment and confirm the pop-up with OK. On the Shipments screen, press Confirm Shipment once Box ID and Tracking Number are set. Click Prepare Invoice. Finally, press Release on the Invoices screen. After the process completes, the order status in both Acumatica and WooCommerce changes to Completed.
Two settings decide what is communicated during those steps. Send Shipment Info during Prepare Invoice sends shipment information to WooCommerce and marks the item as shipped during the prepare invoice process. Send Invoice Info during Release sends invoice information and moves the WooCommerce order to Completed status. The tracking number is updated on the WooCommerce order after Prepare Invoice.
Inventory reacts at defined points as well. After Prepare Invoice, the WooCommerce ordered quantity is reduced from the Available and Available for Shipping quantity fields in Acumatica. After an order refund, the item's quantity is added back to the On Hold, Available, and Available for Shipping fields.
Exporting an order from Acumatica to WooCommerce
The Sales Order screen includes an action for exporting an order to WooCommerce and updating it. Export is supported only for orders with Open, On Hold, and Awaiting Payment statuses, and it works from the mapping configured on the Order Mapping tab. Customer resolution follows a simple rule: if the customer was exported beforehand and carries a Customer ID in the Woo Customer Info tab, the order is created under that ID; otherwise it is created against the Guest customer. Shipping method is exported using the Ship Via mapping from the Cross-References tab. Order status is set to Processing if the sales order has a payment and to On Hold if it does not.
One limitation should be communicated up front: tax export is not currently supported during order export, owing to differences in customer tax zones in WooCommerce. Exporting tax requires Acumatica-to-WooCommerce tax mapping to be configured.
Cancelling a WooCommerce order
The Sales Orders actions menu offers two cancel options that behave very differently. Cancel Order is the standard Acumatica action and cancels only within Acumatica. WooCommerce Cancel Order is the connector's own feature and cancels the WooCommerce order through API requests. Once an order is cancelled on both sides, reopening it in Acumatica does not send a further request to update WooCommerce. If the status is changed manually in WooCommerce and the order retrieved again, it will not appear on the Import WooCommerce Orders screen; it appears on the WooCommerce Orders screen instead, because it already has an associated sales order.
Item Synchronization: The Export Item Processes
Item export is batched for efficiency. During the export process from the Export Item Processes screen, a single API request covers one hundred items, with requests sent before the batch begins.
Item settings that govern creation
On the Item Settings tab, Import Item controls whether new items are created in Acumatica during item synchronization. When it is cleared, the program prohibits import and creation unless the items already exist in Acumatica. The matching logic is worth knowing: the system searches for the Inventory CD using the WooCommerce product SKU, retrieves the item if found, and otherwise displays an error stating that the item does not exist in the system.
Import Item Type specifies the item type to create and UOM is the unit of measure used to quantify inventory items. Last Page Number for Getting Products indicates the last page used when retrieving products. Synchronize Only Changed Items limits the Export WooCommerce Inventory Items screen to items whose details have changed since the last sync. Populate Items in Inventory Details adds items to Inventory Details during import. Use Numbering Sequence for SKU Generation generates a SKU when none is found, provided the numbering sequence exists; without it, and with no SKU on the item, an error appears. The WooCommerce Tax Status and Tax Category ID fields update the WooCommerce item's tax status to match the Acumatica stock item tax category during synchronization.
The five export item processes
Item Sync creates and updates item data in WooCommerce. The process is to select the store code, which is set automatically when Default Store is selected, choose the fields from Item Mapping that should be updated, specify which price fields to export, and then sync items individually, all at once, or on a schedule. Synchronization is bidirectional, so updates can flow either way. Selecting variants of products displays all product variants, and if the system does not find an item in the store during synchronization it creates it automatically. The Is WooCommerce Item checkbox is selected only for items obtained from WooCommerce and generated by the Biz-Tech Services Acumatica WooCommerce connector.
Quantity Sync updates inventory in WooCommerce from Acumatica data. Three requirements must be met for an item to appear: it must already exist as a WooCommerce item in Acumatica, it must be loaded, checked, and saved in the Inventory Details tab of the store, and warehouses and a quantity type must be selected in Warehouse Details. On the processing screen, Quantity is a read-only field showing the item's total across all selected warehouses, while WooCommerce Quantity is editable and specifies what is actually synchronized. That distinction gives you control over what the store sees.
Images Sync exports an item's image when the corresponding checkbox is selected for the product in the Item Mapping tab, exporting the default image configured in the stock item's Description tab, and it handles both products and variants. Item Price updates prices in WooCommerce using either MSRP or Default Price, with the corresponding field value selected in Item Mapping; in both cases it is the Regular Price field on the WooCommerce website that is updated. Publish and Unpublish Item manages product visibility: an item whose status is In Stock is published, and an item with any other status is unpublished. The Selected for Publish/Unpublish field on the Item Details tab controls which items appear on that processing screen. All of these processes can run manually or on a scheduler.
Item Details, categories, and mappings
The Item Details tab loads and manages items directly. Load Acumatica Items retrieves all stock and non-stock items, and Load WooCommerce Items does the same from the store. Sync to WooCommerce exports Acumatica items outward and Sync from WooCommerce imports them inward. Publish Items in WooCommerce gives selected items Published status, while Unpublish changes the status to Last Modified. Check All toggles selection of everything displayed, Purge deletes all items shown in the table, and Get Item By ID retrieves a single WooCommerce item into Acumatica. When an item is synced from Acumatica to WooCommerce, a new item is created there and a unique ID is generated, displayed both in the store screen and on the WooCommerce Inventory tab of Stock Items. The item details list can be exported to and imported from Excel, and synchronization, publishing, and unpublishing can also be performed from the Stock and Non-Stock Items screens.
On the Product Categories tab, Get WooCommerce Categories retrieves categories from the store. To create a category in Acumatica and push it outward, select it, save, then press Sync WooCommerce Categories. Retrieved categories appear on the WooCommerce Categories tab of the stock item screen, where a preferred category can be set and exported with the item, after which WooCommerce selects it automatically. This list can also be exported to and imported from Excel.
The Inventory Mappings tab configures mappings that synchronize Acumatica stock item fields and attribute values with WooCommerce fields. Get WooCommerce Properties loads the product's main fields, meta fields, or attributes. Acumatica Target defines whether a Stock Item or an Attribute is mapped, DAC Name specifies the data access class, and Acumatica Property names the field or attribute. Update in Acumatica and Update in WooCommerce control the direction in which changes apply, Woo Product Level defines whether the WooCommerce field is a main field, attribute, or metadata, and WooCommerce Property names the field loaded by the properties action. One constraint matters here: the connector does not support the mapping function during the Acumatica item export process, only during import from WooCommerce to Acumatica. When exporting an inventory item outward, the item's Inventory CD is set as the SKU.
Item and order mapping tabs
The Item Mappings tab chooses which fields are exported and imported during item sync. The first column holds field names, the Create in Woo column allows those values to be created in WooCommerce, the next column allows updates to values already created there, and Update in Acu applies selected values during import. Some fields, such as SKU, are selected by default because they are required for item creation.
The Order Mappings tab holds the order mapping configuration, loaded and mapped automatically when the preferences screen is saved, and configurable manually thereafter. Load WooCommerce Fields loads or updates all related WooCommerce order fields. Update in WooCommerce and Update in Acumatica control the direction of updates during order synchronization. Original Field indicates an original field, and original fields must be mapped for order synchronization to work. Meta Data should be checked when the WooCommerce target is metadata. Acumatica Target selects between Document for sales order header fields and Details for sales order line fields, Acumatica Property names the field, WooCommerce Field Target specifies Order, Line, or Metadata, and WooCommerce Property names the loaded field.
Template and matrix items
Template items follow their own two-step path. From the Template Items screen, the Sync Template Items to WooCommerce action exports the template, and a successful export generates a WooCommerce Product ID shown under the WooCommerce Product tab. Running Sync Matrix Items to WooCommerce afterward creates the matrix items, which appear as variations under the corresponding template item product in the store.
Customer Synchronization and B2B Mode
One rule frames everything else in this area: individual customers are not imported directly from WooCommerce into Acumatica. Customer information reaches Acumatica through WooCommerce orders instead. When creating a customer during that process, the system searches first by the contact's WooCommerce customer ID, then by billing email, then by account name, and creates a new customer and contact only if no match is found.
In B2B mode, enabled by the B2B Store checkbox, the connector syncs the customer's contact and creates a user in WooCommerce. Before exporting a contact, the system searches for an existing user by the contact's ID, then by email, and finally by a username composed of first and last name. A password must be set on the contact in Acumatica for the export to succeed, and after export the generated WooCommerce ID is written back to the Acumatica contact. If the Woo Customer Info tab is empty and B2B Store is enabled, all contacts are exported as separate users; if B2B Store is not enabled, only the primary contact is exported, falling back to the first available contact when no primary exists.
With B2B Store cleared, standard customer export logic applies, initiated from the Customers screen using the Sync WooCommerce Customer action. The program checks WooCommerce using the customer's email, WooCommerce customer ID, and first and last name combination. If the customer is found, a record is created in the Woo Customer Info tab holding the WooCommerce Customer ID; if not, a new customer is created in the store and its ID written back to the same tab. This process depends on the customer having a corresponding contact, and an error is displayed when one is missing.
Customers can also be linked manually by adding a record on the Customer page, opening the Woo Customer Info tab, and setting the Contact ID, Store Code, WooCommerce Customer ID, and B2B fields. For automatic linking, each customer needs first name, last name, and email, and the record is created automatically during synchronization when the contact's email or first and last name combination matches the WooCommerce username. A dedicated Export WooCommerce Customers processing screen creates and updates customers in the store, individually or all at once, and supports a scheduler.
Refund Processing
Refund handling requires the Use Refund Process checkbox in the store setup. Specify the date from which refunded orders should be retrieved, then click Get Orders, and the system retrieves and displays all matching refunded orders. Refund information is recorded on the Refunds tab of the related WooCommerce order in Acumatica, so the original order and its refund stay linked.
The system then handles refunds according to how far the original order had progressed:
- If the sales order has had no fulfillment activity and consists of a single item, processing generates a payment of Customer Refund type, attaches it to the Payments tab, sets the refunded amount, and closes the order; the sales order status changes to Canceled and its lines are deleted.
- If a shipment was created but not confirmed, the system finds and deletes that shipment, then follows the same path as the first case.
- If a shipment was confirmed, the system creates a credit memo and attaches a reference number of Customer Refund type to the Applications.
- If an invoice was prepared but not released, the system likewise creates a credit memo and attaches a Customer Refund reference number to Applications.
- If the invoice was already released, the system reverses the invoice.
In each case, the Processed checkbox on the Refunds tab of the WooCommerce Orders screen is automatically selected once the work is complete, which means the process is finished and the order is closed. Following the reference number shows the Customer Refund payment and refunded amount on the Application History tab.
Webhooks and Automation Schedules
Selecting Use Webhook adds the Webhook Settings tab. With Use Customer Webhook, Use Product Webhook, and Use Order Webhook selected, the Biz-Tech Services Acumatica WooCommerce integrator generates newly created customers, products, and orders in WooCommerce. Creating a webhook means filling out the webhook name and implementation class on the Acumatica Webhooks screen, saving to generate the webhook URL, and adding that URL in WooCommerce.
For scheduled operation, both the order get and order import processes can be automated. For the get process, configure the Get Orders screen and select Import Orders from WooCommerce in the Screen ID field. For the import process, set up the Import All screen and select Import WooCommerce Orders in the Screen ID field. Most of the export item processes and the customer export screen support schedulers as well.
Where to Monitor WooCommerce Results in Acumatica
When configuring the Biz-Tech Services Acumatica WooCommerce integrator, training users, or investigating a record that did not arrive, these are the fields and screens that reveal what actually happened:
- Test Credentials on WooCommerce Store Preferences, which confirms the connection before anything else is investigated.
- The WooCommerce Status selections on Order Settings, since an order whose status checkbox is not selected is never retrieved.
- Begin Order Date and Last Imported Order Date, which bound what the next import will collect, remembering that orders are selected by updated date rather than created date.
- Which of the two order screens a record appears on, since status routing sends working orders to Import WooCommerce Orders and completed or cancelled ones to WooCommerce Orders.
- Sales Order Number and Invoice Number on the WooCommerce Orders screen, which confirm that import and invoicing actually produced documents.
- The Import Fields tab, which holds the mapped values as captured at Get Order time and is the only place to correct them before import.
- The Delivery Settings field on the Shipping tab of the sales order, which should show the mapped Ship Via value after import.
- Quantity versus WooCommerce Quantity on the quantity sync screen, where the first is the calculated total and the second is what is actually sent.
- The quantity type selected in Warehouse Details, which decides whether On Hand, Available, or Available for Shipment is published to the store.
- The Woo Customer Info tab on the Customers screen, which holds the WooCommerce Customer ID that determines whether an exported order is linked to a real customer or to Guest.
- The Processed checkbox on the Refunds tab, which confirms a refund has been fully handled.
- The Get Order Process Error Messages screen, which collects all errors generated during order retrieval.
- Email error notifications, which alert users to failed imports at the address configured on Order Settings.
WooCommerce Acumatica Integration: Frequently Asked Questions
What does the WooCommerce connector for Acumatica do?
It synchronizes a WooCommerce store with Acumatica ERP in both directions. Inbound, it retrieves orders and creates Acumatica sales orders with their customers, payments, discounts, taxes, and shipping details. Outbound, it exports items, quantities, prices, sales prices, images, categories, and customers, publishes and unpublishes products, and reports shipment and invoice progress back so order status stays current in the store.
Why are some WooCommerce orders not appearing on the import screen?
Check three things. First, the order's status checkbox must be selected in WooCommerce Status on the Order Settings tab, or the order is never retrieved. Second, orders route by status: working statuses appear on the Import WooCommerce Orders screen while canceled, failed, empty, and completed orders appear on the WooCommerce Orders screen. Third, confirm Begin Order Date and Last Imported Order Date cover the period you expect, remembering that selection is by updated date, not created date.
How does payment authorization work between WooCommerce and Acumatica?
WooCommerce authorizes the payment at checkout, verifying the card and reserving funds without collecting them. When the order synchronizes, Acumatica does not authorize again; it performs a post-authorization that records the existing authorization in accounts receivable. The payment is then captured in Acumatica when the order is ready to fulfill. Ebizcharge, Fortis, and other credit card methods are supported, and the matching payment method must exist in Acumatica.
Why was a customer not created in Acumatica from a WooCommerce order?
Most likely because Import Customer and both address override options are unselected, in which case customer data is not imported and the order uses the default Acumatica customer. Note also that individual customers are never imported directly from WooCommerce; customer information only reaches Acumatica through orders.
Which inventory quantity is published to WooCommerce?
Whichever type is selected in the Warehouse Details tab, from On Hand, Available, or Available for Shipment. The system totals that quantity across every warehouse added on that tab. On the quantity sync screen, Quantity is the read-only calculated total while WooCommerce Quantity is editable and determines what is actually sent to the store.
Why did my order mapping change not affect an order?
Because changes to the Order Mapping configuration do not apply to orders that have already been retrieved. The Import Fields tab is populated during the Get Order process using the mapping in force at that moment. To alter an already-retrieved order, edit it manually from the Import Fields tab before importing it into Acumatica.
Can taxes be exported from Acumatica to WooCommerce?
Not currently during the order export process, because of differences in customer tax zones in WooCommerce. Exporting tax on order export requires Acumatica-to-WooCommerce tax mapping to be configured. Taxes on imported orders are handled separately through the tax options on the Order Settings tab, including the option to use an external service such as Avalara.
What is the difference between Cancel Order and WooCommerce Cancel Order?
Cancel Order is the standard Acumatica action and cancels the order only inside Acumatica. WooCommerce Cancel Order is the connector's own action and cancels the order in WooCommerce through API requests. After a WooCommerce cancellation, reopening the order in Acumatica does not send another update to the store.
Work With the Biz-Tech Services WooCommerce Connector
The Biz-Tech Services Acumatica WooCommerce integrator is large, but its shape is simple. Credentials and validated API keys open the connection, the WooCommerce Store screen defines how everything behaves, order settings and status selections determine what comes in and where it lands, customer, payment, discount, and tax options shape the resulting sales order, fulfillment steps push shipment and invoice information back to the store, and the export item processes keep products, quantities, prices, and images current in the other direction. When something does not arrive, the routing rules, the Import Fields tab, and the error message screen tell you where it stopped.
If your business sells through WooCommerce and wants orders, customers, inventory, pricing, and fulfillment synchronized with Acumatica without manual re-keying, we are glad to help you scope, configure, and roll out the connector. Visit https://biz-techservices.com to learn more about our Acumatica integration expertise or to schedule a personalized demonstration of the Biz-Tech Services WooCommerce Connector.
How CRV Lines Flow Through Sales Orders, Shipments, and Invoices in Acumatica
How CRV Lines Flow Through Sales Orders, Shipments, and Invoices in Acumatica
California Redemption Value, or CRV, has to appear on the invoice as its own line, and it has to stay attached to the product that generated it. That is the whole problem CRV processing in Acumatica solves. When a beverage item is added to a sales order, the system automatically creates a second line for its associated CRV item, carries the same quantity and warehouse across, and keeps the two lines linked by parent and child references all the way through shipments and invoices. Understanding where that child line comes from, which fields control whether it appears, and how the link survives downstream is what keeps CRV billing accurate.
The Biz-Tech Services CRV solution for Acumatica handles this automatically rather than asking order entry staff to remember an extra line on every beverage order. This article follows a CRV line through the full Acumatica data flow, from the item configuration that defines it to the invoice where it is billed, and identifies the fields users should monitor at each stage.
What a CRV Item Is in Acumatica
A CRV item in Acumatica is a non-stock item used across the inventory and sales modules to identify products that carry an environmental fee. It is automatically added to sales transactions when you sell beverages that fall under California's recycling program. The distinction that matters most is structural: CRV items are only ever non-stock items. They represent a fee rather than physical goods, so they must never be set up as stock items, and the configuration will not behave correctly if they are.
In practice this means every beverage product you sell has two records behind it. The parent item is the actual product being shipped, and the child CRV item is the environmental fee attached to that product. Acumatica keeps them associated so that pricing, quantity, and downstream document flow stay synchronized.
Why California Redemption Value Matters for Beverage Distributors
California Redemption Value is a refundable deposit applied to eligible beverage containers under the state's beverage container recycling program. Consumers pay the deposit at purchase and recover it when they return the container for recycling. For distributors and retailers in the supply chain, CRV is not revenue in the ordinary sense; it is a pass-through amount that must be charged, tracked, and reported separately from the product price.
That separation is exactly why CRV cannot simply be built into a product's unit price. It needs to be visible as a distinct line on the sales document so that customers can see what they are paying, and so that the business can account for the deposit correctly. Any ERP handling for CRV therefore has to solve two things at once: automatically adding the fee whenever an eligible product is sold, and keeping that fee identifiable as belonging to a specific product line. The Acumatica configuration described below does both.
The CRV Data Flow at a Glance
Before looking at each screen, here is the full path a CRV line travels through Acumatica:
- A CRV item is created as a non-stock item representing the environmental fee.
- On the Stock Items (IN202500) screen, the Price/Cost tab of each eligible beverage product points to its CRV item through the CRV Item field.
- The CRV Amount field on the General tab of the Stock Items screen determines the fee amount based on the selected unit of measure.
- The Include in CRV checkbox on the customer's default location determines whether CRV applies to that customer at all.
- When the parent item is added to a sales order for an eligible customer, Acumatica automatically adds the associated CRV item as a new line with the same quantity and warehouse.
- Parent Item and Child Item fields on the Sales Orders, Shipments, and Invoices screens keep the product and its CRV line identifiable as a pair throughout the document flow.
Each field below sits at one of those handoffs, and knowing which stage a problem occurred at tells you which screen to open.
Step One: Configure the CRV Item as a Non-Stock Item
The flow begins with the fee itself. Before any product can reference a CRV charge, the CRV item must exist in Acumatica as a non-stock item. This is a prerequisite rather than a preference. The CRV Item field described in the next step expects a non-stock item, and configuring the fee as a stock item will break the association.
Businesses selling containers in more than one size category typically need more than one CRV item, since deposit amounts differ by container size under the state program. Setting these up as separate non-stock items, clearly named so that order entry staff and accounting can tell them apart on a document, is worth the small amount of extra effort at configuration time.
Step Two: Link the CRV Item to Its Parent Product
With the fee item in place, each eligible beverage product must be told which CRV item belongs to it. This association is made on the Stock Items screen and is the single most important link in the whole data flow. To configure it, navigate to the Stock Items screen, select the desired item, open the Price/Cost tab, and in the CRV Item field select the appropriate CRV item.
This field is what makes automatic CRV line creation possible. Without it, Acumatica has no way to know which fee applies to which product, and no child line will be generated when the product is sold. When a CRV charge fails to appear on an order, this field is the first place to check.
Step Three: Set the CRV Amount by Unit of Measure
The amount charged is controlled by the CRV Amount field on the General tab of the Stock Items screen. This field determines the amount for the associated CRV item based on the selected unit of measure, which allows a separate price to be defined for the CRV item independently of the product's own price.
The unit of measure dependency deserves attention during setup. Because deposits are levied per container, a product sold in multiple units of measure, such as individual bottles and cases, needs its CRV amount configured so that the resulting charge reflects the number of containers actually being sold. Reviewing this against a real order for each unit of measure you sell is a worthwhile validation step before going live.
Step Four: Enable Include in CRV on the Customer Location
The final piece of configuration determines which customers are charged. An Include in CRV checkbox has been added to the customer default location, and the status of that checkbox controls whether the CRV item is displayed on the sales order for that customer. Selected, and CRV lines are generated. Cleared, and they are not.
Placing this control at the location level rather than at the customer level is deliberate and useful. A customer with several ship-to locations may be subject to the deposit at some and not others, and the location record is where that distinction naturally lives. It also means CRV behavior can be adjusted for a specific customer relationship without touching item configuration that affects everyone.
How CRV Lines Are Created on the Sales Order
With configuration complete, the runtime behavior is simple and automatic. Navigate to the Sales Orders screen and select a customer whose location has the Include in CRV checkbox selected. When the main parent item is added to the order, the system automatically adds the associated CRV item as a new line.
Two attributes are inherited from the parent line rather than being entered by the user: the child CRV line receives the same quantity and the same warehouse as the parent item. This inheritance is what keeps the fee proportional to what is actually being sold. If ten cases are ordered, the CRV line reflects ten, and if the parent line ships from a particular warehouse, the CRV line is associated with that same warehouse. Order entry staff do not need to calculate, add, or adjust anything.
Parent Item and Child Item: Keeping CRV Lines Linked Downstream
A CRV line is only useful if you can tell which product it belongs to, and that becomes harder as documents multiply. To solve this, Parent Item and Child Item fields have been added to the Sales Orders, Shipments, and Invoices screens, specifically to identify the main item and its associated CRV item.
The significance of those three screens together is that the relationship survives the entire order-to-invoice flow. On the sales order, you can see which CRV line was generated by which product. When the order is shipped, the shipment document carries the same parent and child identification. When the invoice is produced, the association is still visible, so the customer's bill can be reconciled line by line and accounting can attribute every deposit to the product that generated it. This is what separates a properly modeled CRV implementation from one where fees appear as anonymous extra lines that nobody can trace.
Where to Monitor CRV Results in Acumatica
When configuring CRV, training users, or investigating an order where the fee looks wrong, these are the fields and screens that show what the system actually did:
- The CRV Item field on the Price/Cost tab of the Stock Items screen, which defines the association between a product and its fee item and is the first thing to check when no CRV line appears.
- The CRV Amount field on the General tab of the Stock Items screen, which sets the fee amount for the selected unit of measure.
- The Include in CRV checkbox on the customer default location, which determines whether CRV lines are generated for that customer at all.
- The non-stock status of the CRV item itself, since CRV items must always be non-stock items.
- The Parent Item and Child Item fields on the Sales Orders screen, which confirm that the generated CRV line is correctly associated with its product.
- The quantity and warehouse on the generated CRV line, which should match the parent line exactly.
- The Parent Item and Child Item fields on the Shipments screen, which confirm the association survived shipment creation.
- The Parent Item and Child Item fields on the Invoices screen, which is where the customer-facing result is verified and where accounting reconciles deposits against products sold.
CRV Processing in Acumatica: Frequently Asked Questions
What is a CRV item in Acumatica?
A CRV item is a non-stock item used in the inventory and sales modules to represent the California Redemption Value environmental fee attached to eligible beverage containers. It is added automatically to sales transactions when you sell beverages covered by California's recycling program, appearing as its own line alongside the product that generated it.
Does a CRV item have to be a non-stock item?
Yes. CRV items are only non-stock items. The fee represents a deposit rather than physical goods, and the CRV Item field on the Price/Cost tab of the Stock Items screen expects a non-stock item. Configuring the CRV item as a stock item will prevent the association from working correctly.
Why is the CRV line not appearing on my sales order?
Check three things in order. First, confirm that the Include in CRV checkbox is selected on the customer's default location, since this controls whether CRV items are displayed on the sales order for that customer. Second, confirm that the parent product has the correct CRV item selected in the CRV Item field on the Price/Cost tab of the Stock Items screen. Third, confirm that the CRV item itself is configured as a non-stock item.
How is the CRV amount determined?
The CRV Amount field on the General tab of the Stock Items screen determines the amount for the associated CRV item based on the selected unit of measure. This allows a separate price to be defined for the CRV item, independent of the product's own price, and lets the charge reflect the number of containers represented by the unit of measure being sold.
How do I tell which CRV line belongs to which product?
Use the Parent Item and Child Item fields, which have been added to the Sales Orders, Shipments, and Invoices screens specifically to identify the main item and its associated CRV item. Because those fields exist on all three screens, the relationship remains visible and traceable from order entry through shipment to the final invoice.
Can CRV be applied to some customers but not others?
Yes. The Include in CRV checkbox sits on the customer default location, so CRV behavior is controlled per location rather than globally. A customer with multiple ship-to locations can have the fee applied at some locations and not at others, without any change to item configuration.
What quantity and warehouse does the CRV line use?
The generated child CRV line inherits both from the parent item automatically. The same quantity and the same warehouse are set on the associated CRV line when the main item is added to the sales order, so the fee stays proportional to what is being sold and no manual adjustment is required during order entry.
Work With the Biz-Tech Services CRV Solution for Acumatica
CRV processing in Acumatica is compact but precise. A non-stock CRV item defines the fee, the CRV Item field on each product creates the association, the CRV Amount field sets the value per unit of measure, the Include in CRV checkbox decides which customers are charged, and the Parent Item and Child Item fields keep the fee traceable to its product across sales orders, shipments, and invoices. Configure those five things correctly and CRV billing takes care of itself on every order that follows.
If your business distributes beverages in California and needs redemption value charges applied automatically and reported accurately, we are glad to help you configure and validate CRV handling in your Acumatica environment. Visit https://biz-techservices.com to learn more about our Acumatica expertise or to schedule a personalized demonstration.
How CRV Lines Flow Through Sales Orders, Shipments, and Invoices in Acumatica
California Redemption Value, or CRV, has to appear on the invoice as its own line, and it has to stay attached to the product that generated it. That is the whole problem CRV processing in Acumatica solves. When a beverage item is added to a sales order, the system automatically creates a second line for its associated CRV item, carries the same quantity and warehouse across, and keeps the two lines linked by parent and child references all the way through shipments and invoices. Understanding where that child line comes from, which fields control whether it appears, and how the link survives downstream is what keeps CRV billing accurate.
The Biz-Tech Services CRV solution for Acumatica handles this automatically rather than asking order entry staff to remember an extra line on every beverage order. This article follows a CRV line through the full Acumatica data flow, from the item configuration that defines it to the invoice where it is billed, and identifies the fields users should monitor at each stage.
What a CRV Item Is in Acumatica
A CRV item in Acumatica is a non-stock item used across the inventory and sales modules to identify products that carry an environmental fee. It is automatically added to sales transactions when you sell beverages that fall under California's recycling program. The distinction that matters most is structural: CRV items are only ever non-stock items. They represent a fee rather than physical goods, so they must never be set up as stock items, and the configuration will not behave correctly if they are.
In practice this means every beverage product you sell has two records behind it. The parent item is the actual product being shipped, and the child CRV item is the environmental fee attached to that product. Acumatica keeps them associated so that pricing, quantity, and downstream document flow stay synchronized.
Why California Redemption Value Matters for Beverage Distributors
California Redemption Value is a refundable deposit applied to eligible beverage containers under the state's beverage container recycling program. Consumers pay the deposit at purchase and recover it when they return the container for recycling. For distributors and retailers in the supply chain, CRV is not revenue in the ordinary sense; it is a pass-through amount that must be charged, tracked, and reported separately from the product price.
That separation is exactly why CRV cannot simply be built into a product's unit price. It needs to be visible as a distinct line on the sales document so that customers can see what they are paying, and so that the business can account for the deposit correctly. Any ERP handling for CRV therefore has to solve two things at once: automatically adding the fee whenever an eligible product is sold, and keeping that fee identifiable as belonging to a specific product line. The Acumatica configuration described below does both.
The CRV Data Flow at a Glance
Before looking at each screen, here is the full path a CRV line travels through Acumatica:
- A CRV item is created as a non-stock item representing the environmental fee.
- On the Stock Items (IN202500) screen, the Price/Cost tab of each eligible beverage product points to its CRV item through the CRV Item field.
- The CRV Amount field on the General tab of the Stock Items screen determines the fee amount based on the selected unit of measure.
- The Include in CRV checkbox on the customer's default location determines whether CRV applies to that customer at all.
- When the parent item is added to a sales order for an eligible customer, Acumatica automatically adds the associated CRV item as a new line with the same quantity and warehouse.
- Parent Item and Child Item fields on the Sales Orders, Shipments, and Invoices screens keep the product and its CRV line identifiable as a pair throughout the document flow.
Each field below sits at one of those handoffs, and knowing which stage a problem occurred at tells you which screen to open.
Step One: Configure the CRV Item as a Non-Stock Item
The flow begins with the fee itself. Before any product can reference a CRV charge, the CRV item must exist in Acumatica as a non-stock item. This is a prerequisite rather than a preference. The CRV Item field described in the next step expects a non-stock item, and configuring the fee as a stock item will break the association.
Businesses selling containers in more than one size category typically need more than one CRV item, since deposit amounts differ by container size under the state program. Setting these up as separate non-stock items, clearly named so that order entry staff and accounting can tell them apart on a document, is worth the small amount of extra effort at configuration time.
Step Two: Link the CRV Item to Its Parent Product
With the fee item in place, each eligible beverage product must be told which CRV item belongs to it. This association is made on the Stock Items screen and is the single most important link in the whole data flow. To configure it, navigate to the Stock Items screen, select the desired item, open the Price/Cost tab, and in the CRV Item field select the appropriate CRV item.
This field is what makes automatic CRV line creation possible. Without it, Acumatica has no way to know which fee applies to which product, and no child line will be generated when the product is sold. When a CRV charge fails to appear on an order, this field is the first place to check.
Step Three: Set the CRV Amount by Unit of Measure
The amount charged is controlled by the CRV Amount field on the General tab of the Stock Items screen. This field determines the amount for the associated CRV item based on the selected unit of measure, which allows a separate price to be defined for the CRV item independently of the product's own price.
The unit of measure dependency deserves attention during setup. Because deposits are levied per container, a product sold in multiple units of measure, such as individual bottles and cases, needs its CRV amount configured so that the resulting charge reflects the number of containers actually being sold. Reviewing this against a real order for each unit of measure you sell is a worthwhile validation step before going live.
Step Four: Enable Include in CRV on the Customer Location
The final piece of configuration determines which customers are charged. An Include in CRV checkbox has been added to the customer default location, and the status of that checkbox controls whether the CRV item is displayed on the sales order for that customer. Selected, and CRV lines are generated. Cleared, and they are not.
Placing this control at the location level rather than at the customer level is deliberate and useful. A customer with several ship-to locations may be subject to the deposit at some and not others, and the location record is where that distinction naturally lives. It also means CRV behavior can be adjusted for a specific customer relationship without touching item configuration that affects everyone.
How CRV Lines Are Created on the Sales Order
With configuration complete, the runtime behavior is simple and automatic. Navigate to the Sales Orders screen and select a customer whose location has the Include in CRV checkbox selected. When the main parent item is added to the order, the system automatically adds the associated CRV item as a new line.
Two attributes are inherited from the parent line rather than being entered by the user: the child CRV line receives the same quantity and the same warehouse as the parent item. This inheritance is what keeps the fee proportional to what is actually being sold. If ten cases are ordered, the CRV line reflects ten, and if the parent line ships from a particular warehouse, the CRV line is associated with that same warehouse. Order entry staff do not need to calculate, add, or adjust anything.
Parent Item and Child Item: Keeping CRV Lines Linked Downstream
A CRV line is only useful if you can tell which product it belongs to, and that becomes harder as documents multiply. To solve this, Parent Item and Child Item fields have been added to the Sales Orders, Shipments, and Invoices screens, specifically to identify the main item and its associated CRV item.
The significance of those three screens together is that the relationship survives the entire order-to-invoice flow. On the sales order, you can see which CRV line was generated by which product. When the order is shipped, the shipment document carries the same parent and child identification. When the invoice is produced, the association is still visible, so the customer's bill can be reconciled line by line and accounting can attribute every deposit to the product that generated it. This is what separates a properly modeled CRV implementation from one where fees appear as anonymous extra lines that nobody can trace.
Where to Monitor CRV Results in Acumatica
When configuring CRV, training users, or investigating an order where the fee looks wrong, these are the fields and screens that show what the system actually did:
- The CRV Item field on the Price/Cost tab of the Stock Items screen, which defines the association between a product and its fee item and is the first thing to check when no CRV line appears.
- The CRV Amount field on the General tab of the Stock Items screen, which sets the fee amount for the selected unit of measure.
- The Include in CRV checkbox on the customer default location, which determines whether CRV lines are generated for that customer at all.
- The non-stock status of the CRV item itself, since CRV items must always be non-stock items.
- The Parent Item and Child Item fields on the Sales Orders screen, which confirm that the generated CRV line is correctly associated with its product.
- The quantity and warehouse on the generated CRV line, which should match the parent line exactly.
- The Parent Item and Child Item fields on the Shipments screen, which confirm the association survived shipment creation.
- The Parent Item and Child Item fields on the Invoices screen, which is where the customer-facing result is verified and where accounting reconciles deposits against products sold.
CRV Processing in Acumatica: Frequently Asked Questions
What is a CRV item in Acumatica?
A CRV item is a non-stock item used in the inventory and sales modules to represent the California Redemption Value environmental fee attached to eligible beverage containers. It is added automatically to sales transactions when you sell beverages covered by California's recycling program, appearing as its own line alongside the product that generated it.
Does a CRV item have to be a non-stock item?
Yes. CRV items are only non-stock items. The fee represents a deposit rather than physical goods, and the CRV Item field on the Price/Cost tab of the Stock Items screen expects a non-stock item. Configuring the CRV item as a stock item will prevent the association from working correctly.
Why is the CRV line not appearing on my sales order?
Check three things in order. First, confirm that the Include in CRV checkbox is selected on the customer's default location, since this controls whether CRV items are displayed on the sales order for that customer. Second, confirm that the parent product has the correct CRV item selected in the CRV Item field on the Price/Cost tab of the Stock Items screen. Third, confirm that the CRV item itself is configured as a non-stock item.
How is the CRV amount determined?
The CRV Amount field on the General tab of the Stock Items screen determines the amount for the associated CRV item based on the selected unit of measure. This allows a separate price to be defined for the CRV item, independent of the product's own price, and lets the charge reflect the number of containers represented by the unit of measure being sold.
How do I tell which CRV line belongs to which product?
Use the Parent Item and Child Item fields, which have been added to the Sales Orders, Shipments, and Invoices screens specifically to identify the main item and its associated CRV item. Because those fields exist on all three screens, the relationship remains visible and traceable from order entry through shipment to the final invoice.
Can CRV be applied to some customers but not others?
Yes. The Include in CRV checkbox sits on the customer default location, so CRV behavior is controlled per location rather than globally. A customer with multiple ship-to locations can have the fee applied at some locations and not at others, without any change to item configuration.
What quantity and warehouse does the CRV line use?
The generated child CRV line inherits both from the parent item automatically. The same quantity and the same warehouse are set on the associated CRV line when the main item is added to the sales order, so the fee stays proportional to what is being sold and no manual adjustment is required during order entry.
Work With the Biz-Tech Services CRV Solution for Acumatica
CRV processing in Acumatica is compact but precise. A non-stock CRV item defines the fee, the CRV Item field on each product creates the association, the CRV Amount field sets the value per unit of measure, the Include in CRV checkbox decides which customers are charged, and the Parent Item and Child Item fields keep the fee traceable to its product across sales orders, shipments, and invoices. Configure those five things correctly and CRV billing takes care of itself on every order that follows.
If your business distributes beverages in California and needs redemption value charges applied automatically and reported accurately, we are glad to help you configure and validate CRV handling in your Acumatica environment. Visit https://biz-techservices.com to learn more about our Acumatica expertise or to schedule a personalized demonstration.



































