Requires the ecommerce-integrations add-on
Manage add-onsThe snag
Amazon sellers reconcile settlement reports by hand every 14 days and only discover pricing or fee variances weeks later.
How Zivvy helps
The ecommerce-integrations add-on polls Amazon SP-API for orders and settlement reports and posts them into /v1/sales-orders and /v1/payment-entries.
Before Zivvy
Handoffs go missing, owners are unclear, audits get painful.
What you get
- Orders + FBA shipments mirrored into /v1/sales-orders
- Settlement reports posted as bulk /v1/payment-entries
- SKU-level fees split into per-item /v1/expense-claims
Workflow stream
Amazon Order → /v1/sales-orders with marketplace_id
Common uses
01
Amazon Order → /v1/sales-orders with marketplace_id
02
Settlement Report → /v1/payment-entries with fees breakdown
03
FBA shipment → /v1/stock-entries.material-transfer
Integration code
Open API referencePost an Amazon order
curl -X POST https://integrate.zivvy.xyz/v1/sales-orders \
-H "Authorization: Bearer $ZIVVY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"customer": "Amazon Marketplace",
"external_id": "amzn-113-1234567",
"source": "amazon",
"items": [{ "item_code": "SKU-001", "qty": 1, "rate": 49.00 }]
}'Sync from SP-API
from sp_api.api import Orders
from zivvy import Zivvy
zv = Zivvy(api_key=os.environ["ZIVVY_API_KEY"])
for order in Orders().get_orders(CreatedAfter="2026-07-01").payload["Orders"]:
zv.sales_orders.create({
"external_id": order["AmazonOrderId"],
"customer": "Amazon Marketplace",
"source": "amazon",
})API endpoints
POST /v1/sales-ordersPOST /v1/payment-entriesPOST /v1/stock-entries
Events emitted
HMAC-SHA256 signed webhooks, retried for 24 hours.
- sales-orders.submitted
- payment-entries.created
- stock-entries.submitted
0
free seats forever
0
card required to start
1
workspace for the workflow
Questions
Ready to try it?
Free plan. Two seats. No card.