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 / Database · Two-way sync platform
Amazon Seller Central and MariaDB integration
Bring supported Amazon Seller Central data into MariaDB for your team's workflows and reporting. This connector supports updates from Amazon Seller Central to MariaDB.
- Field mappings and sync direction under your control
- Inspect and resolve record errors in one dashboard
Source-to-destination updates for supported objects
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
Example workflow
Sales order reporting workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting eventA change involving Amazon Seller Central Orders or the proposed sales order table in MariaDB needs a defined result in the other system.
Start with Amazon Seller Central Orders and the proposed sales order table in MariaDB. 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 multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Review records and field ownershipMapping essentials
Records and field ownership
Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.
Download the mapping worksheetCSV · No email required
| Amazon Seller Central record | MariaDB record | Record matching | Field ownership |
|---|---|---|---|
| OrdersProposed record; confirm Stacksync object support.Reporting dataset | Proposed sales order tableProposed table; choose its name and schema. | 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. |
| Listings / Catalog ItemsProposed record; confirm Stacksync object support.Reporting dataset | Proposed product or catalog item tableProposed table; choose its name and schema. | Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. | Assign ownership for catalog content, price, and stock separately. |
| FBA InventoryProposed record; confirm Stacksync object support.Reporting dataset | Proposed inventory or stock position tableProposed table; choose its name and schema. | Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient. | Choose the stock authority and distinguish available, reserved, and physical quantities. |
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Why teams connect Amazon Seller Central and MariaDB
Put your Amazon Seller Central and MariaDB data to work
Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one Amazon Seller Central and MariaDB workflow to test, define what success looks like, and decide who handles failed updates.
Power internal dashboards from MariaDB views over Orders and Shipments.
Audit historical changes to Listings / Catalog Items using system-versioned tables.
Consolidate marketplace and in-house data in one MariaDB database without custom API code.
What records can you sync?
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
MariaDB
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| See connector requirements. Confirm field permissions and sync direction. |
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 | MariaDB |
|---|---|---|
| Integration interface | REST API (Selling Partner API, SP-API) | SQL wire protocol (MySQL-compatible client/server protocol) |
| Authentication | SP-API app credentials | Database credentials |
| Change detection | Historical and incremental syncs are documented. | Stacksync creates database triggers for change logging. |
| Read access | Available for supported records | Available for supported records |
| Write access | Not supported by this connector | Available for supported records |
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.
MariaDB
- Integration interface
- SQL wire protocol (MySQL-compatible client/server protocol)
- Authentication
- Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host)
- Change detection
- Stacksync creates database triggers for change logging. Trigger permissions and binary-log settings must allow their creation.
- Read access
- Available for supported records
- Write access
- Available for supported records
Setup requirements
- Use one auto-generated primary key per selected table and grant the connected user the required table permissions.
- Verify that Stacksync can create triggers. When binary logging is enabled, an administrator may need to enable log_bin_trust_function_creators.
Limitations to check
- Composite keys are unsupported and schema/table/column renames require a sync configuration update.
Technical documentation
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Prepare Amazon Seller Central and MariaDB 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
MariaDB setup checklist
- Use one auto-generated primary key per selected table and grant the connected user the required table permissions.
- Verify that Stacksync can create triggers. When binary logging is enabled, an administrator may need to enable log_bin_trust_function_creators.
Setup guides: Authorize MariaDB
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 MariaDB 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
Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheet · CSV, no email required
Reporting dataset
Orders / Proposed sales order table in MariaDB (choose its name)
Plan a sales order dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- Amazon Seller Central
- Object support to establish
- MariaDB
- Your database schema
- 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 documentation
Reporting dataset
Listings / Catalog Items / Proposed product or catalog item table in MariaDB (choose its name)
Plan a product or catalog item dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- Amazon Seller Central
- Object support to establish
- MariaDB
- Your database schema
- Record identity
- Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
- Field ownership
- Assign ownership for catalog content, price, and stock separately.
Fields to include
- Source product ID
- SKU or variant reference
- Description
- Unit of measure
- Price-list reference
- Record dependencies
- Resolve units, variants, categories, and applicable price lists before order lines.
- Validation
- Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
- Recovery
- Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
References: Amazon Seller Central: Listings / Catalog Items documentation
Reporting dataset
FBA Inventory / Proposed inventory or stock position table in MariaDB (choose its name)
Plan a inventory or stock position dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- Amazon Seller Central
- Object support to establish
- MariaDB
- Your database schema
- Record identity
- Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient.
- Field ownership
- Choose the stock authority and distinguish available, reserved, and physical quantities.
Fields to include
- Product reference
- Location reference
- Quantity type
- Quantity
- As-of time
- Record dependencies
- Resolve product, unit, warehouse/location, and lot/serial references.
- Validation
- Test the same SKU in two locations, a reservation, and an older snapshot arriving late.
- Recovery
- Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
References: Amazon Seller Central: FBA Inventory documentation
Reporting dataset
Shipments / Proposed shipment or fulfillment table in MariaDB (choose its name)
Plan a shipment or fulfillment dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- Amazon Seller Central
- Object support to establish
- MariaDB
- Your database schema
- 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 documentation
Reporting dataset
Financial Events / Proposed event or activity table in MariaDB (choose its name)
Plan a event or activity dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- Amazon Seller Central
- Object support to establish
- MariaDB
- Your database schema
- Record identity
- Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key.
- Field ownership
- Decide whether the destination stores an immutable history or only a current-state summary.
Fields to include
- Source event ID
- Event type
- Occurred-at time
- Related record ID
- Payload version
- Record dependencies
- Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID.
- Validation
- Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior.
- Recovery
- Identify side effects already completed before replaying an event; use the agreed deduplication key.
References: Amazon Seller Central: Financial Events documentation
Compare integration approaches
Use Amazon Seller Central Orders and MariaDB Proposed sales order table in MariaDB (choose its name) for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Stacksync managed sync
- Best fit
- Source-to-destination updates for supported objects. Choose the records, writable fields, and permissions for your workflow.
- 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: Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. 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 MariaDB 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 / Proposed sales order table in MariaDB (choose its name), update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when Amazon Seller Central and MariaDB need a transformation, approval, or action outside a direct record sync.
- 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.
File or scheduled snapshot
- Best fit
- Consider for a one-time Amazon Seller Central / MariaDB 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 reporting workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Orders or Proposed sales order table in MariaDB (choose its name) record needs a defined result in the other system.
- Start with Amazon Seller Central Orders and MariaDB Proposed sales order table in MariaDB (choose its name). 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.
Product or catalog item reporting workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Listings / Catalog Items or Proposed product or catalog item table in MariaDB (choose its name) record needs a defined result in the other system.
- Start with Amazon Seller Central Listings / Catalog Items and MariaDB Proposed product or catalog item table in MariaDB (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve units, variants, categories, and applicable price lists before order lines.
- 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 two variants of one product, a changed SKU, and a price that applies to only one market or currency.
If it fails: Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
Inventory or stock position reporting workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected FBA Inventory or Proposed inventory or stock position table in MariaDB (choose its name) record needs a defined result in the other system.
- Start with Amazon Seller Central FBA Inventory and MariaDB Proposed inventory or stock position table in MariaDB (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve product, unit, warehouse/location, and lot/serial 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 the same SKU in two locations, a reservation, and an older snapshot arriving late.
If it fails: Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
Coordinate Amazon Seller Central commerce data with MariaDB
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A catalog, order, or fulfillment change in Amazon Seller Central matters to a selected destination dataset.
- Choose the commerce entity from Orders or Listings / Catalog Items; separate products, variants, orders, and fulfillments.
- Preserve order and line references through the MariaDB process. Define many-to-one or one-to-many relationships explicitly.
- Assign separate ownership for commercial approval, inventory, and fulfillment, including partial cancellations or returns.
Expected result: A split fulfillment and repeated request preserve line quantities without duplicate orders or shipments.
If it fails: Look up existing downstream records before retrying creation; reconcile current order and fulfillment states.
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 / Proposed sales order table in MariaDB (choose its name)
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.
Listings / Catalog Items / Proposed product or catalog item table in MariaDB (choose its name)
Test case
Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
Expected result
The expected product or catalog item relationship is preserved with no duplicate action or unintended write.
FBA Inventory / Proposed inventory or stock position table in MariaDB (choose its name)
Test case
Test the same SKU in two locations, a reservation, and an older snapshot arriving late.
Expected result
The expected inventory or stock position relationship is preserved with no duplicate action or unintended write.
Shipments / Proposed shipment or fulfillment table in MariaDB (choose its name)
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
Verify read access in Amazon Seller Central and write access in MariaDB. Test the permitted route without relying on a return sync.
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 MariaDB Proposed sales order table in MariaDB (choose its name), 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 product or catalog item change
Investigate
Inspect Amazon Seller Central Listings / Catalog Items and MariaDB Proposed product or catalog item table in MariaDB (choose its name), their IDs, and the destination error.
Next action
Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
Rejected or repeated inventory or stock position change
Investigate
Inspect Amazon Seller Central FBA Inventory and MariaDB Proposed inventory or stock position table in MariaDB (choose its name), their IDs, and the destination error.
Next action
Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
A record type or update is unavailable
Investigate
Check the Amazon Seller Central and MariaDB 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 MariaDB
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 MariaDB Timing depends on the connected systems
Detect changesHistorical and incremental syncs are documented. The guide does not specify a universal detection interval.
Apply updatesSelected writable fields update in MariaDB. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
MariaDB Amazon Seller Central Direction not supported
Detect changesThis route requires read access from MariaDB 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 MariaDB integration FAQ
-
The documented direction is Amazon Seller Central to MariaDB for supported objects. Amazon Seller Central is documented as a read-only connector, so it cannot receive write-back through this connector. Authorize both systems, map the selected fields, and validate the first load and later changes.
-
Amazon Seller Central is read-only through Stacksync. Two-way sync is not supported through these connectors; use a supported direction or review another implementation.
-
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. Use one auto-generated primary key per selected table and grant the connected user the required table permissions. Use the pair worksheet to record ownership and acceptance criteria.
-
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 Proposed sales order table in MariaDB (choose its name) in MariaDB. 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.
-
Use Amazon Seller Central Orders and MariaDB Proposed sales order table in MariaDB (choose its name) for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 405 integrations listed for Amazon Seller Central and MariaDB.
Next step
See your workflow in Stacksync
Walk through your Amazon Seller Central and MariaDB records, field mappings, and requirements with an integration engineer.
