Print to order
Exactly what was sold goes into the queue, in the quantity ordered. Right for bulky items and made to order work.
Every paid Shopify order becomes a print job in SimplyPrint automatically. You map your products to a print file once, and after that the work is waiting at the printer before you would have thought about the order yourself.
Print on demand lives or dies by the gap between the order and the printer. A bed that sits idle overnight because nobody saw the order is nine hours you cannot get back, and the customer is waiting for exactly those nine hours. This connector takes the gap out: the order becomes a job while you are asleep.
A printed product is rarely one print. It is parts, and a bed rarely makes exactly one of each. So the interesting work is arithmetic: how many of this part go into one item, and how many usable ones come off one bed. You set those two numbers per file once, and after that a sale turns into the right number of jobs without anyone counting.
Only paid orders get this far. Cancelled orders and refunded units are taken off first, so no filament goes into something that will not go through.
The queue group and the filament colour travel with each job, arriving as a material tag in SimplyPrint, so the work lands on the right printer in the right colour without anyone checking it again. A file is only ever queued once per order line, so a retry can never print the same thing twice.
Printing one at a time is wasteful for an item a bed makes eight of. In stock mode nothing happens while your Shopify inventory stays above the threshold you set per product. Drop below it and Schakel tops the shelf up, exactly to the threshold and no further.
The reprinted units are added back in Shopify, so the shelf your shop sells from is the shelf the printers actually filled.
Exactly what was sold goes into the queue, in the quantity ordered. Right for bulky items and made to order work.
Nothing until the threshold is crossed, then a batch. Right for small parts a bed makes many of at once.
Six things, all of them checkable afterwards in the queue history.
The moment a Shopify order is paid, its files land in the SimplyPrint queue. Unpaid orders are left alone and refunded units are taken off the order first, so no filament and no printer hours go into something that is not settled.
Put the EAN in the filename between parentheses, for example Flexi Dragon (8712345678901), and your whole catalogue maps to the right print files in one go. Whatever does not match you point at yourself, and that choice is kept.
Map every part an item is made of. Per file you set how many go into one item and how many usable ones one print produces, and the number of jobs is worked out from those two numbers.
Jobs can land in a fixed queue group, and per product you can send a filament colour along, which arrives as a material tag in SimplyPrint.
What was lined up is recorded per order line and per print file, and that can only happen once. A line that was skipped or failed does keep retrying, because it has not been printed yet.
It is skipped with the reason written in the queue history, and the number of products without a file sits on your dashboard. Map the file later and the next run picks it up.
| Task | By hand | With Schakel |
|---|---|---|
| Noticing a new order | Checking the shop between prints | Queued the moment it is paid |
| Finding the right file | Digging through folders | Mapped by barcode, once |
| Working out how many prints | Counting parts and beds in your head | From the two numbers you set per file |
| Setting the filament colour | Remembered, or not | Sent along as a material tag |
| Choosing the printer | Whichever is free | The queue group you assigned |
| An unpaid order | Sometimes printed anyway | Left alone until it is paid |
| Refilling a thin shelf | Noticed when it is empty | Topped up at your threshold |
| A product with no print file | Quietly forgotten | Counted on your dashboard |
The third one is the only one that takes real time, and the barcode match does most of it for you.
You connect your store to Schakel once. If you already run another Shopify connector, that same connection is reused rather than asked for again.
In SimplyPrint, under your account on the API tab, you will find an API key and your Company ID. You enter those two under Connections, and we test them right away rather than finding out later.
Import your catalogue and click match by barcode. Anything that does not match automatically you point at yourself, from your folders in SimplyPrint, and per file you set how many go into an item and how many one print yields.
Print on every order, or only when stock drops below a threshold. After that it keeps pace, and the queue history shows exactly what was lined up and why anything was skipped.
Connect the store, paste the key, map your files. That is the whole setup.
Your SimplyPrint key and Company ID are stored encrypted, and the Shopify connection runs through Shopify itself. Access can be revoked from either side at any time.
Not sure how to get those keys? Step by step:
On app.schakel.app, with your own Schakel account. No webshop required.
Shopify and SimplyPrint is one of many. Pick two systems and see what travels between them.
It is skipped, with the reason written next to it in the queue history. The number of products without a file sits on your dashboard so it does not stay unnoticed. Map the file later and the next run picks it up.
You choose. Print to order and exactly what was sold goes into the queue. Print to stock and nothing happens while your stock stays above your threshold; Schakel only tops it up when it would drop below.
No. What was lined up is recorded per order line and per print file, and that can only happen once. A line that was skipped or failed does keep retrying, because it has not been printed yet.
Refunded units are taken off the order before anything is queued. If it was already printed, that stands; you remove it from the queue in SimplyPrint yourself.
Yes. Schakel connects through the official APIs of Shopify and SimplyPrint, so you install nothing on your own server and nothing travels outside those two parties.
SimplyPrint needs a full delivery address to make a label. If the country and postcode do not match up, that shipment is held and shows in the log, rather than a wrong label coming out.
Yes. Which carrier and shipping method SimplyPrint uses you set there; Schakel only hands the shipment over complete.
It comes across, so SimplyPrint matches what was actually settled and you correct nothing by hand.
We use cookies to measure how the site is used and to improve our advertising. Necessary cookies are always on.