Seller Central shows you orders. It does not open a print job, check a buyer’s file, reorder blanks or tell you what a product really earned. We build that layer on the Selling Partner API, around the way your workshop or warehouse actually runs.
Each item links to the client project where we built it. Most sellers start with order import and routing, then add stock and profit once the orders flow.
Orders from every marketplace land in one list. Each new order is sent to the right production line, warehouse or person by rules your staff can edit.
Your own blanks or raw stock and your FBA stock in the same view, with a warning before something runs out.
Revenue is easy to see in Seller Central. Margin is not. We deduct what each sale really costs and show the result per product and per marketplace.
The checks a person used to do on every order become rules that run on their own and stop the order only when something is wrong.
When stock comes from suppliers, the purchase can be part of the order flow: buy, track, receive, bill.
Sales, net profit and the items that need attention on one screen, so the daily check happens in one place instead of a tour of browser tabs.
Aspect has printed custom mugs, shirts, puzzles and canvases in Zhytomyr, Ukraine, since 2000. Most of its sales now come through Amazon Custom, so most orders carry the buyer’s own artwork. Staff downloaded those files by hand, checked their resolution one by one and retyped orders into the workshop’s tracking.
These facts come from Amazon’s SP-API documentation, checked in October 2026. Each card links to the page it comes from. They decide how the sync is structured long before the first screen is drawn.
SP-API access is granted by role. A developer requests roles in the developer profile, Amazon approves or denies each one, and an application can only use roles approved for that profile. Calling an operation without the right role returns a 403.
When a seller authorizes the app, it receives a refresh token. The app exchanges it at the Login with Amazon (LWA) token endpoint for an access token, which is sent in the x-amz-access-token header.
In Orders API v0, operations that return buyer personal data, such as getOrderBuyerInfo and getOrderAddress, need a Restricted Data Token (RDT) from the Tokens API. Orders API v2026-01-01 replaces v0, lets apps skip the Tokens API step for PII, and v0 users must migrate by March 27, 2027.
SP-API rate limits use a token bucket. Tokens refill at a set rate per second up to a burst limit, and each request uses one. Most limits apply per selling partner and application pair. A throttled request gets HTTP 429, which is safe to retry.
The Notifications API pushes events to an Amazon SQS queue or Amazon EventBridge. ORDER_CHANGE fires on important order changes such as status updates and buyer cancellations. FBA_INVENTORY_AVAILABILITY_CHANGES fires when FBA quantities change. Both use the SQS workflow.
A report is requested with createReport, then checked with getReport until its status is DONE, CANCELLED or FATAL. A DONE report returns a document ID for the data. Reports can also run on a schedule, and REPORT_PROCESSING_FINISHED can signal completion over SQS.
Peak days are when throttling, late events and bad files show up together. This is how we build for them, with the projects where each safeguard runs today.
We key each imported order on its Amazon order ID and update the existing record when it comes back. A push event and a scheduled sync can see the same order without creating a second job.
Calls go through a client-side limiter per seller and operation. On a 429 the job waits and retries instead of hammering the endpoint. Sync work runs in background jobs, not on a user’s screen.
Push events are fast, but Amazon itself advises having another way to fetch data if delivery is delayed. A scheduled pull on a fixed interval fills the gap and keeps stock counts honest.
Checks run before work starts, not after. A low-resolution file holds the order and the buyer is asked for a better one, so a weak image never reaches the printer.
Charges and cost deductions are tied to real events in the order lifecycle, using real product and shipping values, so balances match what actually happened.
Routing rules, taxes, fees and exchange rates are admin settings with their own history. Changing a rule is a form, not a deployment.
Marketplace orders are only half the job when stock comes from suppliers. Peregrine Ship, a Hong Kong logistics company, runs a dropshipping and fulfillment platform. OSKI worked on it from June 2024 to July 2025, with automated sourcing from China’s 1688 marketplace at the center.
The same pattern fits an Amazon seller who restocks from suppliers. More on this kind of work in logistics software development.
Read the Peregrine Ship case
“They maintained reliability without needing constant oversight, which made the collaboration efficient.”
The slowest part of an Amazon project is often not the code. It is waiting on role approval or finding out late that a field you need sits behind a restricted operation. We check both at the start.
Related: e-commerce development for the wider order and fulfillment back office, integrations and automation for other systems, and QuickBooks integration when sales and costs need to reach the books. If the back office itself needs replacing, see ERP development and our guide to a two-way QuickBooks sync for a custom ERP.
From the moment a buyer pays on Amazon to the moment the parcel ships and the margin is known. Each manual step, file download and spreadsheet goes on the list.
Developer profile, roles, and whether any restricted roles are needed for buyer data. Approval is Amazon’s decision, so it starts before the build, not after.
Routing rules, stock thresholds, which costs go into the profit view and who is alerted when an order is held. You approve them before we write code.
Usually order import and routing. Then stock, then profit. Each phase is demoed on real orders from your account.
Amazon changes APIs, fees and usage plans. We support the integration in production and update it when they do.
Amazon print on demand, supplier sourcing, catalog sync and an order-driven back office.
A platform that pulls orders from 7 Amazon marketplaces, turns personalized orders into print jobs and shows the real margin on every product.
A sourcing step that buys from 1688 suppliers for each order, tracks the shipment and bills clients only when each stage is complete.
Faster, safer bulk imports to WooCommerce for ProdUp, plus a data quality dashboard and multi-language product editing.
A custom ERP that brings inventory, order processing, purchasing and reporting together and keeps vendor data in sync with QuickBooks.
Shopify connects to NetSuite through Oracle's NetSuite Connector, Celigo's integration app, other apps or a custom build. We compare what each syncs and costs, list the failure points (variants, tax, discounts, refunds, payouts) and price a custom build.
The best ERP for retail and fashion brands handles size and color matrices, one stock pool across stores, web and wholesale, and clean sync with your POS and marketplaces. We compare seven options by data model, integrations and price.
The best ecommerce ERP is the one that keeps one stock number across every channel and routes orders without manual work. We compare six options by channel connectors, inventory sync and price, and show when a custom order layer wins.
Anything missing? Send us your question and an engineer will answer, usually within one business day.
Contact usIf an existing tool covers your flow, start there. It is cheaper. A custom SP-API integration makes sense when your process is specific to you: personalized orders that become production jobs, your own routing rules, a profit view that includes your materials and reprints, or a link to your own ERP or supplier. Aspect needed all four, which is why its platform is custom.
We recommend the seller’s own company holds the developer profile and the credentials, so access stays with you. Amazon describes private developers as those who build applications that integrate only their own company. Registration starts in Seller Central under Apps and Services, then Develop Apps, or in the Solution Provider Portal for migrated accounts. We help prepare the role requests, including restricted roles if buyer data is needed.
Yes. For Aspect, orders from 7 Amazon marketplaces in the US, UK and EU sync into one dashboard every 15 minutes. Plan for differences per region: Amazon notes that usage plans can vary by store and region.
We have no Shopify case to show yet. We have shipped WooCommerce work for ProdUp, and our order and stock logic is not tied to Amazon. If you sell on Shopify too, we will review its API against your flow before we quote, and tell you plainly if we see a risk.
Where the supplier has an API, yes. For Peregrine Ship the platform places orders through the 1688 marketplace API, imports tracking numbers and updates stock on arrival. About 30% of the manual order flow was replaced by automated actions.
It depends on four things: whether Amazon has approved the roles you need, how many marketplaces and order types you sell, how much logic sits between the order and the shipment, and which other systems must connect, such as a supplier or QuickBooks. After we map one order and review access, you get a fixed estimate for the first phase.
You do. Code, databases and API credentials live in your accounts, with full IP assignment in the contract. We charge for the work, not per order or per marketplace.
A spec, a Figma file or three paragraphs is enough to start.
Cookies on oski.solutions
We'd like to use analytics cookies to understand how the site is used, and marketing cookies to measure our ads. They are off unless you allow them. You can change your choice any time via “Cookie settings” in the footer. Cookie policy
