Amazon Seller Central
Read-only connector
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| See connector requirements. Confirm field permissions and sync direction. |
Business productivity / ERP · Two-way sync platform
Amazon Seller Central and SuiteAnalytics integration
Both connectors are read-only. Review a shared reporting destination or another method for application updates.
Set this up from Claude or ChatGPT- Scope your workflow with an integration engineer
- Review the systems, records, and updates you need
Integration planning
stacksync.com Built for teams where self-serve, reliability and scale matter
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Proposed workflow
Sales order process handoff
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving Amazon Seller Central Orders or SuiteAnalytics Invoice needs a defined result in the other system.
Start with Amazon Seller Central Orders and SuiteAnalytics Invoice. Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
Review records and field ownershipAI assistant
Set up Amazon Seller Central and SuiteAnalytics from Claude or ChatGPT
Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.
1. Add the Stacksync MCP server
Server URL
https://mcp.stacksync.com/mcp In Claude
- Open Customize → Connectors, select + Add, then Add custom connector.
- Name it Stacksync and enter https://mcp.stacksync.com/mcp.
- Select Connect, sign in to Stacksync and choose your workspace.
In ChatGPT
- Open Settings → Apps → Advanced settings and turn on Developer mode.
- Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
- Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
Set up Codex or Claude Code
Codex
codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksyncComplete the browser sign-in with your Stacksync account, then start a new Codex session.
Claude Code
claude mcp add --transport http stacksync https://mcp.stacksync.com/mcpOpen Claude Code, run /mcp, select stacksync and complete the browser sign-in.
Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.
Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.
2. Ask your assistant
Create a sync between my Amazon Seller Central and SuiteAnalytics.
Also from the same chat
You can also ask for workflows and AI agents (Genies) that use Amazon Seller Central and SuiteAnalytics. The assistant checks what each app supports, for example:
- “Build a workflow that messages our team in Slack when a Amazon Seller Central record changes.”
- “Create a Genie that answers questions about our SuiteAnalytics data in Slack.”
What happens next
- Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
- Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
- Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.
New to Stacksync? Create an account first, then sign in from your assistant.
Proposed record relationships
Records to connect
Use these examples to define record matching and field ownership for your technical review.
Download the mapping worksheetCSV · No email required
| Amazon Seller Central record | SuiteAnalytics record | Record matching | Field ownership |
|---|---|---|---|
| OrdersProposed record; confirm Stacksync object support.Business process handoff | InvoiceDocumented record: Supported | Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order. | Finance owns invoice posting; the order system supplies the approved commercial context. |
| OrdersProposed record; confirm Stacksync object support.Business process handoff | Item FulfillmentDocumented record: Supported | Link the order and selected line IDs to separate fulfillment IDs; allow split shipments. | The fulfillment owner decides when an approved order can ship and how cancellations are handled. |
| OrdersProposed record; confirm Stacksync object support.Record matching | Sales OrderDocumented record: Supported | Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. | Decide which system approves the order and which can cancel or amend it after fulfillment begins. |
These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.
What records can you sync?
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
SuiteAnalytics
Read-only connector
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| Reading: Supported. Updating this object: confirm availability. |
| Supported. Confirm field permissions and sync direction. |
| Reading: Request access. Updating this object: confirm availability. |
Connection essentials
Review how each system connects, detects changes, and permits access to your records.
View setup requirements and limits| Connection requirement | Amazon Seller Central | SuiteAnalytics |
|---|---|---|
| Integration interface | REST API (Selling Partner API, SP-API) | SQL over ODBC, JDBC, and ADO.NET (SuiteAnalytics Connect) |
| Authentication | SP-API app credentials | NetSuite token-based authentication with integration credentials, access token, account ID, and a role with SuiteAnalytics permissions. |
| Change detection | Historical and incremental syncs are documented. | The saved Stacksync guide does not specify the change-detection mechanism. |
| Read access | Available for supported records | Available for supported records |
| Write access | Not supported by this connector | Not supported by this connector |
Enterprise controls
Security and control for your integrations
Explore security controlsCompliance and data transfers
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
- SOC 2 Type II
- ISO 27001
- HIPAA BAA
- GDPR
- CCPA
- DPF US-EU-UK-CH
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Record-level recovery
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Technical reference
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
Amazon Seller Central
- Integration interface
- REST API (Selling Partner API, SP-API)
- Authentication
- SP-API app credentials (LWA client ID/secret, application ID, Merchant ID/Seller ID token, refresh token, region) entered into the Stacksync connection form
- Change detection
- Historical and incremental syncs are documented. The guide does not specify a universal detection interval.
- Read access
- Available for supported records
- Write access
- Not supported by this connector
Setup requirements
- Supply SP-API authorization credentials, merchant identification, region, and refresh token using the connector authorization guide.
- Include client-secret renewal in operations planning; the saved setup guide specifies six-month expiration.
Limitations to check
- The documented connector sends data out of Amazon; it does not document write-back to Amazon.
Technical documentation
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
SuiteAnalytics
- Integration interface
- SQL over ODBC, JDBC, and ADO.NET (SuiteAnalytics Connect)
- Authentication
- NetSuite token-based authentication with integration credentials, access token, account ID, and a role with SuiteAnalytics permissions.
- Change detection
- The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
- Read access
- Available for supported records
- Write access
- Not supported by this connector
Setup requirements
- Have a NetSuite administrator enable SuiteAnalytics Connect and token-based authentication.
- Create an integration, access token, and role with the SuiteAnalytics Connect permissions listed in the authorization guide.
Limitations to check
- SuiteAnalytics is a read-only route. Use a separately supported NetSuite connector for write-back requirements.
Technical documentation
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Prepare Amazon Seller Central and SuiteAnalytics access
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Amazon Seller Central setup checklist
- Supply SP-API authorization credentials, merchant identification, region, and refresh token using the connector authorization guide.
- Include client-secret renewal in operations planning; the saved setup guide specifies six-month expiration.
Setup guides: Authorize Amazon Seller Central
SuiteAnalytics setup checklist
- Have a NetSuite administrator enable SuiteAnalytics Connect and token-based authentication.
- Create an integration, access token, and role with the SuiteAnalytics Connect permissions listed in the authorization guide.
Setup guides: Authorize SuiteAnalyticsNetSuite SuiteAnalytics Connect
Prepare to go live
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the Amazon Seller Central and SuiteAnalytics planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Record identity and field ownership
Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.
Download the mapping worksheet · CSV, no email required
Business process
Orders / Invoice
Order-to-invoice handoff: Amazon Seller Central Orders provides context for SuiteAnalytics Invoice. These are related records, not equivalent entities.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Amazon Seller Central
- Object support to establish
- SuiteAnalytics
- Documented record · Supported
- Record identity
- Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order.
- Field ownership
- Finance owns invoice posting; the order system supplies the approved commercial context.
Fields to include
- Source record reference
- Destination record reference
- Approved handoff state
- Duplicate-detection key
- Record dependencies
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Validation
- Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
- Recovery
- Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
References: Amazon Seller Central: Orders documentationSuiteAnalytics: Invoice documentation
Business process
Orders / Item Fulfillment
Order-to-fulfillment handoff: Amazon Seller Central Orders provides context for SuiteAnalytics Item Fulfillment. These are related records, not equivalent entities.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Amazon Seller Central
- Object support to establish
- SuiteAnalytics
- Documented record · Supported
- Record identity
- Link the order and selected line IDs to separate fulfillment IDs; allow split shipments.
- Field ownership
- The fulfillment owner decides when an approved order can ship and how cancellations are handled.
Fields to include
- Source record reference
- Destination record reference
- Approved handoff state
- Duplicate-detection key
- Record dependencies
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Validation
- Test partial fulfillment, an out-of-stock line, and a repeated request that must not create a second shipment.
- Recovery
- Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
References: Amazon Seller Central: Orders documentationSuiteAnalytics: Item Fulfillment documentation
Record matching
Orders / Sales Order
Compare whether Amazon Seller Central Orders and SuiteAnalytics Sales Order describe the same sales order in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Amazon Seller Central
- Object support to establish
- SuiteAnalytics
- Documented record · Supported
- Record identity
- Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
- Field ownership
- Decide which system approves the order and which can cancel or amend it after fulfillment begins.
Fields to include
- Source order ID
- Customer reference
- Line references and quantities
- Order status
- Currency
- Record dependencies
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Validation
- Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
- Recovery
- Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
References: Amazon Seller Central: Orders documentationSuiteAnalytics: Sales Order documentation
Record matching
Shipments / Item Fulfillment
Compare whether Amazon Seller Central Shipments and SuiteAnalytics Item Fulfillment describe the same shipment or fulfillment in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Amazon Seller Central
- Object support to establish
- SuiteAnalytics
- Documented record · Supported
- Record identity
- Retain shipment/fulfillment and line IDs, order reference, and carrier context.
- Field ownership
- The fulfillment owner controls shipped quantities and cancellation eligibility.
Fields to include
- Source shipment ID
- Order/line references
- Carrier
- Tracking reference
- Fulfillment status
- Record dependencies
- Resolve order lines, delivery address, carrier, and any partial-fulfillment references.
- Validation
- Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order.
- Recovery
- Verify existing fulfillment before retrying creation; reconcile quantities against order lines.
References: Amazon Seller Central: Shipments documentationSuiteAnalytics: Item Fulfillment documentation
Compare integration approaches
Choose a method around one example record and the update your business needs. Use Orders / Invoice to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Stacksync managed sync
- Best fit
- Review compatibility with a Stacksync engineer using an example of the records and updates you need.
- Operating responsibility
- Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
- Before you choose
- Check record matching: Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order. Verify field coverage, deletion handling, and how changes are detected.
Native vendor integration
- Best fit
- A vendor-built integration may fit if it supports your Amazon Seller Central and SuiteAnalytics record types.
- Operating responsibility
- Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
- Before you choose
- First check whether either vendor offers this integration. If available, verify Orders / Invoice, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider explicit orchestration for the Orders / Invoice handoff.
- Operating responsibility
- Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
- Before you choose
- Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.
File or scheduled snapshot
- Best fit
- Consider for a one-time Amazon Seller Central / SuiteAnalytics migration or a reporting need with an explicit freshness window.
- Operating responsibility
- Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
- Before you choose
- Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.
Workflow scenarios and expected results
Sales order process handoff
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Orders or Invoice record needs a defined result in the other system.
- Start with Amazon Seller Central Orders and SuiteAnalytics Invoice. Use the record-matching and field-ownership rules from your mapping worksheet.
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Sales order process handoff
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Orders or Item Fulfillment record needs a defined result in the other system.
- Start with Amazon Seller Central Orders and SuiteAnalytics Item Fulfillment. Use the record-matching and field-ownership rules from your mapping worksheet.
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test partial fulfillment, an out-of-stock line, and a repeated request that must not create a second shipment.
If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Sales order sync test
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Orders or Sales Order record needs a defined result in the other system.
- Start with Amazon Seller Central Orders and SuiteAnalytics Sales Order. Use the record-matching and field-ownership rules from your mapping worksheet.
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Reconcile SuiteAnalytics business records with Amazon Seller Central
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A finance-owned record in SuiteAnalytics needs operational visibility through Orders or Listings / Catalog Items.
- Select Customer or Vendor with the correct legal entity, period, and currency.
- Define a reporting relationship in Amazon Seller Central; do not equate customer records, ledger accounts, and posted transactions.
- Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.
Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.
If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.
Initial load and acceptance testing
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Orders / Invoice
Test case
Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Orders / Item Fulfillment
Test case
Test partial fulfillment, an out-of-stock line, and a repeated request that must not create a second shipment.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Orders / Sales Order
Test case
Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Shipments / Item Fulfillment
Test case
Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order.
Expected result
The expected shipment or fulfillment relationship is preserved with no duplicate action or unintended write.
Direction and permissions
Test case
Neither connector can receive writes. If the goal is combined reporting, select a separate writable destination and retain each source record ID.
Expected result
Only an approved, supported direction and permitted fields are written.
Freshness and reconciliation
Test case
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
Expected result
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failed updates, retries and recovery
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Rejected or repeated sales order change
Investigate
Inspect Amazon Seller Central Orders and SuiteAnalytics Invoice, their IDs, and the destination error.
Next action
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Rejected or repeated sales order change
Investigate
Inspect Amazon Seller Central Orders and SuiteAnalytics Item Fulfillment, their IDs, and the destination error.
Next action
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Rejected or repeated sales order change
Investigate
Inspect Amazon Seller Central Orders and SuiteAnalytics Sales Order, their IDs, and the destination error.
Next action
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
A record type or update is unavailable
Investigate
Check the Amazon Seller Central and SuiteAnalytics connector guides, account permissions, and any operations marked On Request.
Next action
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Source and destination disagree after a retry
Investigate
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Next action
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
Change detection and update delivery
How updates move between Amazon Seller Central and SuiteAnalytics
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Amazon Seller Central SuiteAnalytics Direction not supported
Detect changesThis route requires read access from Amazon Seller Central and write access to SuiteAnalytics; the documented connector restrictions do not permit it.
Apply updatesUse a supported direction or review a separate integration method for this requirement.
SuiteAnalytics Amazon Seller Central Direction not supported
Detect changesThis route requires read access from SuiteAnalytics and write access to Amazon Seller Central; the documented connector restrictions do not permit it.
Apply updatesUse a supported direction or review a separate integration method for this requirement.
Update timing and record limits
- Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
FAQ
Amazon Seller Central and SuiteAnalytics integration FAQ
-
Both Amazon Seller Central and SuiteAnalytics are documented as read-only Stacksync connectors. Neither can receive the other system's changes through these connectors. Use a supported writable destination for reporting, or review a separate integration method if the workflow requires changes in either application.
-
Amazon Seller Central and SuiteAnalytics are read-only through Stacksync. Two-way sync is not supported through these connectors; use a supported direction or review another implementation.
-
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
-
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
-
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
-
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
-
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
-
Start by reviewing Orders in Amazon Seller Central and Invoice in SuiteAnalytics. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
-
Choose a method around one example record and the update your business needs. Use Orders / Invoice to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Supply SP-API authorization credentials, merchant identification, region, and refresh token using the connector authorization guide. Have a NetSuite administrator enable SuiteAnalytics Connect and token-based authentication. Use the pair worksheet to record ownership and acceptance criteria.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 352 integrations listed for Amazon Seller Central and SuiteAnalytics.
Popular · 5 of 352
-
Amazon Seller Central and Linnworks -
Amazon Seller Central and Logiwa WMS -
SuiteAnalytics and Docusign -
SuiteAnalytics and Monday -
SuiteAnalytics and Notion
No integrations match .
Next step
Plan your integration with an engineer
Walk through your Amazon Seller Central and SuiteAnalytics records, field mappings, and requirements with an integration engineer.
