DL-025 · Case study
One print-file engine for several personalised-product sellers
Several sellers of personalised products laid out Amazon Custom orders by hand. We adapted one print-file engine to each of them: orders in, print-ready batches out.
- Client
- Name withheld
- Location
- United States
- Industry
- Personalised products
- Capabilities
- 03Build
01
Challenge
- Personalised orders were laid out for print one at a time, by hand.
- Each seller had a different product: label sheets, badges or ribbons.
- Buyer customisation data arrives in separate files, not in the order.
02
Environment
- Owner-run sellers using Amazon Custom.
- Production on laser cutters and printers with fixed sheet layouts.
- Private SP-API apps, each with its own restricted-data approval.
03
Intervention
- Read orders and Amazon Custom customisation files per ASIN through SP-API.
- Rendered print-ready PDFs with cut-contour spot colours for laser cutting.
- Adapted layouts per product: badge sheets, label grids, ribbon print tables.
- Delivered batches to cloud storage, grouped by design for download.
04
Outcome
- Sellers print ready-made batches instead of handling single orders.
- Each new seller starts from a proven engine, not from scratch.
- Production kept running through Amazon's Orders API migration.
- 01SELLER CENTRALAmazon Custom→SP-APIOrders
- 02SP-APIOrders→PRINT ENGINEShared coreorders
- 03CUSTOM FILESBuyer text / images→PRINT ENGINEShared corecustomisation
- 04LAYOUT RULESPer product- -PRINT ENGINEShared core
- 05PRINT ENGINEShared core→CLOUD STORAGEBatches by designprint-ready PDFs
- 06CLOUD STORAGEBatches by design→CUTTER / PRINTERProduction
Stack and services.
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→