Skip to content

Order-to-print automation for 3D print farms: a guide

Orders arrive from several channels; printing happens in one workshop. This is how to automate the steps in between, and which ones should stay with a person.

AMENT Research TeamPublished 11 min read

One queue

Short answer

Order-to-print automation gathers store orders into a single production queue, links each product to an approved print file and hands the work to planning. Done well, new orders reach production on their own, products without a file show up in a list, and an order cancelled in the store is put on hold rather than silently deleted. AMENT Hive does this for Shopify, ikas, Trendyol and manual orders; writing order status back to the store is off by default and still being validated in the field.

Key takeaways

  • Get every channel into one queue first; planning, files and printers only make sense after that.
  • Tie each SKU to one approved print profile, and keep a visible list of products that have no file yet.
  • An order cancelled in the store should be held in production, not deleted, so a person can decide.
  • Use a marketplace shipping deadline as the plan's due date, and make it impossible to miss when it is close.
  • Writing status back to a store changes what customers see, so it should start switched off and ask per order.

Why do orders get lost on a print farm?

On a small farm the order flow usually lives in one person's head. There is a new package on Trendyol, two orders on the Shopify store and a custom colour request in an Instagram message. The owner writes them into a notebook or spreadsheet, remembers which file prints which product with which settings, and walks to the printers.

That works up to about five printers. As orders and channels multiply, the same mistakes start to repeat. The trouble is rarely the printers. It is the gap between an order and a build plate.

  • Scattered channels: every store has its own dashboard, and forgetting one tab is enough to miss an order.
  • File choice from memory: which 3MF prints which product, on which printer and in which colour is written down nowhere.
  • Hidden deadlines: the marketplace's shipping deadline sits in its dashboard, not on the production list.
  • Silent cancellations: the customer cancels, but there is a half-printed plate on a printer and nobody knows.
  • Double entry: the same order goes into a spreadsheet and a notebook; one gets updated, the other goes stale.

This guide first describes the general problem and what a good flow looks like. Then it explains how AMENT Hive handles these steps today, which parts are live and which are still being validated in the field.

What does order-to-print automation actually mean?

Order-to-print automation is not "let the machine do everything". It means handing the repetitive, error-prone steps to software and keeping a person on the steps that need judgement or a hand on the printer. The chain has roughly six links.

  1. 1

    Intake

    Orders from every channel are converted to one shape and enter one queue.

  2. 2

    Matching

    Each product code (SKU) on the order is tied to the approved print file for that product.

  3. 3

    Planning

    Matched lines become plates and are spread across suitable printers.

  4. 4

    Slicing

    The file is sliced for the printer it is going to, with colours mapped to that printer's slots.

  5. 5

    Printing

    The file goes to the printer; starting the print is always a person's confirmation.

  6. 6

    Close-out

    The operator enters good units, anything short goes back into the plan, and the order moves to packing.

This post focuses on the first two links and the exceptions around them: intake, matching products to files, cancellations and feedback to the store. For planning see our guide to plate planning, and for slicing the post on cloud slicing for print farms.

A manual flow compared with an automated one
StepDone by handRiskAutomated
Collecting ordersEach dashboard opened in turnA missed orderChannels land in one queue
Choosing the fileFrom memory or a folderWrong version or colourSKU tied to an approved profile
DeadlineIn the marketplace dashboardLate-shipping penaltiesOn the order and in the plan
CancellationDeleted, if noticedWasted print timePut on hold with an alert

The last link is often skipped, yet that is where an automation earns trust. In Hive the operator enters good units when a plate finishes, and any shortfall goes back into the plan on its own. Parts rejected at quality control are added to the order as reprints. So every order in the queue knows how many good parts it still needs.

Bringing Shopify, ikas and Trendyol orders into one queue

The point of a single queue is simple: whichever channel an order comes from, production should see it the same way. Order number, channel, line items, quantities, promised date and, where there is one, a shipping deadline. Channel-specific detail stays in the background.

ChannelsOne queueProduct → fileProductionTrendyolAPI + webhookikasAPI + webhookShopifywebhookManual orderform#5521TY24 H#1188IK#2043SH#0007MN#5530TYSKU matchApproved filePlanDraftUnmatchedNo print file yetOn holdCancelled in storeNever silently deleted:a person decides.
From channels into one queue, then to product matching and the plan. Products without a print file and orders cancelled in the store take a separate path.

How channels connect in Hive

  • ikas: you create a private app in the ikas admin and enter its Client ID and Client Secret in Hive. Hive registers the order notifications itself, imports open orders from the last 14 days, then checks for missed orders every 10 minutes.
  • Trendyol: you enter the Seller ID, API Key and API Secret from the seller panel's integration details. Open packages from the last 13 days come in, notifications are registered, and the 10-minute check runs as well. Each Trendyol package becomes one Hive order.
  • Shopify: signed webhooks for order created, updated, paid and cancelled are set up in the Shopify admin, and Hive verifies the signature on every one.
  • Manual orders: for work that arrives by message, phone or at a fair, the form on the Orders page is always available.

If the same notification arrives twice, or an older copy turns up after newer information, Hive recognises it: the order is not duplicated and old data does not overwrite new. Orders still waiting for payment or confirmation are visible but do not enter production yet. All of this is live (✅).

Promised dates and Trendyol's shipping deadline

For each store connection you set the promise to customers in working days, and orders from that store get their promised date from it. Trendyol also sends the latest time the package must be handed to the carrier. Hive shows it on the order as "Ship by" and turns it red when less than 24 hours remain.

Planning takes whichever of the two dates is earlier as the due date. So even when your own promise looks comfortable, the marketplace's shipping rule really drives the plan. For the wider picture of marketplace selling, see our guide to selling 3D printed products online.

Mapping each SKU to an approved print file

This is the heart of the automation. If there is no written link between the store's "Cable organiser, black" and the workshop's "cable_v3_6up.3mf", every order depends on someone's memory. Once the link is written down, the moment an order arrives it is clear what to print.

In Hive that link is called a print profile. A profile ties together the SKU (optionally a variant attribute such as colour), the print file, the printer model, nozzle size, material, units per plate, plate time and grams. A new profile starts as a draft; an owner or production manager has to approve it before production uses it.

The unmatched products list

Adding a product to the store and forgetting its print profile is very common. The coverage view on Hive's catalog page lists every SKU on open orders and flags the ones without an approved file. The planner leaves those lines out and shows them separately as "could not be planned: no approved print profile". From the list, one click takes you to adding a profile for that SKU.

  1. 1

    Upload the file

    Upload the product's 3MF to the catalog. If you upload the same file twice, Hive recognises it and stores it once.

  2. 2

    Create the profile

    Pick the SKU, printer model, nozzle and material; enter units per plate and plate time.

  3. 3

    Approve it

    An owner or production manager approves the profile. Only then does the planner use it.

  4. 4

    Check coverage

    Fill the gaps until the catalog says every open order line has an approved print file.

Cancellations and edits: never silently delete production work

The most dangerous place in any automation is where a change in the outside world flows straight into production. Ignoring work because the customer cancelled sounds sensible. But at that moment there may be a half-printed plate on a printer and finished parts on a shelf waiting to be packed.

Silent deleteHive: put on holdPrintingCancelled in storeJob vanishes from listHalf a part on the plate,nobody knows why.PrintingCancelled in storeOn hold + alertCancelFinishThe plan flags plates ofheld orders; a start isrefused until you decide.
Top: the cancellation flows straight into production and the job disappears. Bottom: the order is put on hold and a person decides.

In Hive, an order cancelled in the store while it is in production is never silently deleted. It moves to "On hold" and the order shows an alert: cancelled in the store while in production, decide whether to cancel or finish it. A similar alert appears when line items change in the store or the payment is refunded. This protection is live (✅).

  • The plan flags plates that belong to held or cancelled orders with "the plan no longer matches the farm".
  • If a plate carries parts for a held order, a request to start that plate is refused.
  • When you change the status by hand the alert clears, and who made the decision is logged.

Writing status back to the store: why it starts switched off

The last link is telling the store the order is ready. Done by hand, that is one more dashboard visit. Done automatically, it changes something the customer sees, and a wrong "shipped" is a hard promise to take back.

Hive has this feature, marked 🧪: it is live, and validation with real stores is still under way. This is how it works:

  • Off by default. The owner has to switch it on for the store connection.
  • One confirmation per order. When an order reaches packing, an owner or production manager presses the button and confirms. There is no bulk or automatic sending.
  • Trendyol: the package is marked "Picking", and "Invoiced" too if you enter an invoice number. "Shipped" is set by Trendyol's carrier when it scans the package; Hive never sets it.
  • ikas: the order can be marked as shipped.
  • Once only: status is sent once per order, and every attempt is logged.

Setting up order-to-print on your own farm

Whatever tool you use, the order of work is the same: collect the channels, tie products to files, then plan and print. In Hive, the order side of that setup looks like this.

HiveOverviewOrdersPlanningCatalogPrintersEvery channel, one queueOrders+ Manual orderOrderChannelDueStatus#5521TrendyolShip by 6 hPrinting#1188ikasDue 18 OctPlanned#2043ShopifyDue 19 OctOn hold#0007ManualDue 21 OctReady#2043 · attentionCancelled in the store while in production; put on hold.CancelFinish anyway
A simplified drawing of Hive's order list with sample data: channel, due date, a red shipping deadline and an order put on hold.
  1. 1

    Connect your stores

    On the Integrations page connect ikas, Trendyol or Shopify, and set the promise to customers in working days for each.

  2. 2

    Check what arrived

    Open orders from the recent past land in the queue within minutes. Check the channel and deadline columns.

  3. 3

    Complete the catalog

    Create and approve a profile for every SKU the coverage list shows without a file.

  4. 4

    Draft the first plan

    On the Planning page generate a draft, review it on the timeline and approve it.

  5. 5

    Test the cancel path

    Cancel a test order in the store and watch it move to On hold in Hive.

You can try Hive free for 14 days, no card needed. If you would like to set it up and run the first orders together, we do that too; plans and pricing are here.

Frequently asked questions

How quickly do Trendyol orders appear in Hive?

When you connect, open packages from the last 13 days are imported. After that Trendyol's order notifications arrive straight away, and Hive also checks every 10 minutes for anything missed. Each package appears in Hive as one order with its shipping deadline.

What happens if a product has no print file?

The order enters the queue, but that line is not planned. It shows on the catalog's coverage list and on the planning screen as having no approved print profile. Once you create and approve the profile, the line is included in the next plan.

If a customer cancels, does the print stop automatically?

No. If the order is in production it is put on hold with an alert, and the print on the printer is left alone. A new print of a plate that belongs to the order cannot be started. A person decides whether to cancel or finish it.

Can Hive mark an order as shipped in the store?

On Trendyol, no: Hive sends at most "Picking" and, with an invoice number, "Invoiced"; the carrier sets "Shipped". On ikas the order can be marked as shipped. The feature is off by default, asks for confirmation per order and is still being validated in the field.

Can I add orders that come in by message or phone?

Yes. The manual order form on the Orders page takes the customer, promised date and line items. A manual order is matched, planned and tracked exactly like a store order.

Run your print farm with AMENT Hive

Try Hive free for 14 days; no card needed.