Commerce · 10 pre-built actions
Amazon Seller integration with Nexus
Bring Amazon Seller fulfilment into governed operations. Fulfilment by Amazon and fulfilment by merchant actions connect marketplace operations to ERP, finance and service.
Pre-built actions
What you can automate
10 pre-built Amazon Seller actions, grouped by what they work on.
10
PRE-BUILT ACTIONS
- 01FBA actions work with Fulfilment by Amazon operations.
- 02FBM actions work with merchant-fulfilled operations.
- 03Marketplace steps join ERP and finance steps in one run.
Workflow
How it fits into a Nexus workflow
Amazon Seller steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Amazon Seller API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Marketplace orders to ERP
Merchant-fulfilled orders are validated and created in your ERP.
Fulfilment exceptions
FBA or FBM exceptions open a task for the operations owner.
Stock alignment
Fulfilment data is compared with ERP items on a schedule.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Industry use cases
Processes that use Amazon Seller
Enterprise
Amazon marketplace to ERP fulfilment
FBA and FBM fulfilment context reaches NetSuite with items checked and exceptions held for review.
Enterprise
Multi-channel commerce to ERP
Shopify and Amazon activity is normalized into one NetSuite flow with one exception path.
Enterprise
Marketplace sales to accounting
Marketplace activity is reflected in NetSuite and reconciled in Xero, with differences approved by finance.
Enterprise
Amazon fulfilment exception workflow
Fulfilment problems become owned ServiceNow tickets, with the owner told and the resolution recorded.
Enterprise
Unified commerce operations
Storefront and marketplace activity flows into Odoo and Xero through one governed process.
Enterprise
Commerce analytics pipeline
Storefront and marketplace data becomes one analytics dataset in Snowflake.
FAQ
Amazon Seller connector questions
- Which Amazon Seller actions are pre-built?
- Nexus includes 10 pre-built Amazon Seller actions across FBA (5) and FBM (5).
- Can Amazon Seller start a workflow?
- Runs that use Amazon Seller start from a webhook, a schedule or another trigger source. Amazon Seller steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Amazon Seller API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- NetSuite connector
Invoices, contracts and items.
- Shopify connector
Orders, customers, products and inventory.
- Human-in-the-loop
Where approval belongs in a running workflow.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Amazon Seller fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.