Discuss a project

DL-022 · Case study

Early FBA inbound tool on Amazon's Inbound API v2024

A multi-brand Amazon seller had to plan large FBA shipments on Amazon's new inbound API before the old workflow was retired. We built one of the first tools on it.

Client
Name withheld
Location
US West
Industry
Multi-brand Amazon seller and distributor
Capabilities
03Build
01

Challenge

  • Amazon was retiring the v0 inbound workflow the shipment process relied on.
  • Inbound API v2024 was new, with almost no production tools built on it.
  • Large shipments needed box, pallet and Transparency labels without manual work.
02

Environment

  • Shipments of thousands of boxes across many brands and SKUs.
  • Catalogue with FNSKU, Transparency and expiry-date requirements.
  • Warehouse labelling on Zebra printers.
03

Intervention

  • Inventory manager synced from Amazon: catalogue, FNSKU, Transparency and expiry flags.
  • Drafts from Excel, box configuration, inbound plans, packing groups and placement options.
  • Transportation step: small-parcel and LTL options, partnered carriers, delivery windows.
  • Labels including Transparency codes, printed to Zebra printers in one click.
04

Outcome

  • Inbound plans run end to end on the v2024 API.
  • Shipments of nearly 5,000 boxes planned and labelled in one tool.
Shipment drafts and catalogue data from SP-API feed an inbound planner that creates plans, placement and transportation on Inbound API v2024, fetches Transparency codes and prints labels to Zebra printers, replacing the retired v0 workflow.supersededplacement, transportcodesone-click printSHIPMENT DRAFTSExcel / manualSP-API CATALOGFNSKU / flagsINBOUND V0RetiredINBOUND PLANNERDjango / ReactINBOUND API V2024Plans / transportTRANSPARENCY APIUnit codesZEBRA PRINTERSBox / pallet labels
  1. 01SHIPMENT DRAFTSExcel / manualINBOUND PLANNERDjango / React
  2. 02SP-API CATALOGFNSKU / flagsINBOUND PLANNERDjango / React
  3. 03INBOUND V0RetiredINBOUND API V2024Plans / transportsuperseded
  4. 04INBOUND PLANNERDjango / ReactINBOUND API V2024Plans / transportplacement, transport
  5. 05TRANSPARENCY APIUnit codesINBOUND PLANNERDjango / Reactcodes
  6. 06INBOUND PLANNERDjango / ReactZEBRA PRINTERSBox / pallet labelsone-click print
Fig. 01Inbound planning on API v2024Shipment drafts and catalogue data from SP-API feed an inbound planner that creates plans, placement and transportation on Inbound API v2024, fetches Transparency codes and prints labels to Zebra printers, replacing the retired v0 workflow.Scale NTS

Results, as published.

~5,000
Boxes in the largest shipments

Stack and services.

Stack08

  • Amazon SP-API
  • Python
  • Django
  • Celery
  • Redis
  • React
  • PostgreSQL
  • AWS CDK

Services used02

Tell us what has to work.

A senior engineer reads every brief. Describe the system, what it runs on today and what happens when it fails.

Discuss a project