Enterprise use case · Amazon Seller + NetSuite
Amazon marketplace to ERP fulfilment
Marketplace fulfilment and ERP records are reconciled by hand, so item and invoice gaps surface late. FBA and FBM fulfilment context reaches NetSuite with items checked and exceptions held for review.
Systems involved
What each system contributes
10 actions
- FBA5
- FBM5
38 actions
- Base8
- Invoices10
- Items10
- Contracts10
Amazon Seller pre-built actions cover FBA and FBM fulfilment operations. Marketplace data outside those actions is read through the Amazon Selling Partner API and normalized in Rules + Code. No Amazon trigger is used: a schedule, HTTP poll or webhook starts the run.
Architecture
One governed run
How it starts: A schedule or HTTP poll starts the run. Amazon Seller has no trigger source.
Step by step
How the process runs
- 01
Fulfilment context
FBA and FBM actions return fulfilment details for the period.
- 02
Validate
Rules + Code maps marketplace items to NetSuite items and checks quantities.
- 03
ERP record
NetSuite Base, Items and Invoices actions create or update records. Contracts are referenced where a channel agreement applies.
- 04
Exceptions
Unmapped items or quantity gaps stop before the ERP write.
Control
Human decision and exception path
Human decision
Operations approves item mappings and any invoice adjustment before NetSuite changes.
Exception path
- Unmapped marketplace items route to item owners.
- Duplicate invoice writes are blocked.
- API throttling is retried with backoff.
Evidence
What gets audited
- Fulfilment data read.
- Mapping and validation result.
- Approval.
- NetSuite record references.
Nexus runs on premises, in private or sovereign cloud, or air-gapped. Credentials stay in the vault, roles decide who can approve, and the execution record stays inside your deployment boundary.
Sovereignty and deploymentRelated
Patterns, connectors and next steps
- Shopify-NetSuite integration
Integration pattern · Storefront orders and inventory stay aligned with ERP invoicing and items.
- Amazon Seller connector
10 pre-built actions
- NetSuite connector
38 pre-built actions
- Enterprise automation
Governed processes across the systems you already run.
- Order to cash across CRM, ERP and billing
Another enterprise use case.
FAQ
Questions about this use case
- Does Nexus replace any of these systems?
- No. Each system keeps its own records. Nexus runs the process between them and records each decision.
- How does the run start?
- A schedule or HTTP poll starts the run. Amazon Seller has no trigger source.
- What if a step is not covered by a pre-built action?
- Amazon Seller pre-built actions cover FBA and FBM fulfilment operations. Marketplace data outside those actions is read through the Amazon Selling Partner API and normalized in Rules + Code. No Amazon trigger is used: a schedule, HTTP poll or webhook starts the run.
Use case review
Discuss this use case
Bring your version of the process. We will map the systems, approvals and evidence it needs.