How to connect Qikink to your ecommerce website
Two credentials, a SKU mapping that does the real work, and the sandbox run you should not skip.
The short version: get your Client ID and client secret from Qikink, set up each product with its artwork in your Qikink dashboard to get a SKU, and put that SKU on the matching product in your store. Paid orders then push automatically. The mapping is the part that matters — get a SKU wrong and the wrong thing gets printed.
TL;DR
- • Two credentials: Client ID and client secret, exchanged for an access token.
- • Artwork lives in Qikink, not in the integration. Your store references a SKU.
- • Sandbox and live are separate environments with separate credentials.
- • Only paid orders should push. Pushing on order placement prints things nobody paid for.
- • Rehearse in sandbox before going live. A misprint is real money.
Step 1 — Get your credentials
Qikink issues a Client ID and a client secret, which are exchanged for an access token used on subsequent calls. If you are building this yourself, cache the token and refresh it on expiry rather than minting one per request.
Qikink runs separate sandbox and live environments on different hosts, with different credentials. Store which mode you are in alongside the credentials — a merchant who has been testing in sandbox and thinks they are live is the failure you are designing against.
Step 2 — Set up products in Qikink first
This is the step people try to skip, and it is the one that makes the integration reliable.
Create each product in your Qikink dashboard with its artwork, print position and garment choice. Qikink gives you a SKU. That SKU is the contract between your store and the printer.
Uploading artwork through an API at order time sounds more elegant and is materially more fragile — a failed upload becomes an order that cannot be printed, discovered after the customer has paid. Artwork living with the printer, referenced by SKU, is the path that just works.
Step 3 — Map SKUs onto your products
In your store, put the Qikink SKU in the product's SKU field. That is the whole mapping.
Check it twice for anything with variants. A size or colour mapped to the wrong SKU produces a confidently printed, confidently shipped, completely wrong item — and print-on-demand has no returns shelf to absorb that.
Step 4 — Push on payment, never on placement
Print-on-demand should be triggered by a paid order, not by an order being placed. The difference is not academic.
If you push on placement, an abandoned online payment sends a real print job to a real printer who bills you for a real t-shirt nobody bought. On a cash-on-delivery order it is worse: you have printed and shipped something before anyone committed to paying for it.
Push on payment confirmation, and make it idempotent so a retried webhook cannot print the same order twice.
Automatic is correct here, and only here. Qikink prints *and* ships, so there is no human step to insert. That is the opposite of a courier integration, where you should push each order by hand because you are the one packing the parcel and a booked courier charge is not refundable.
The errors you are most likely to hit
| Symptom | Usual cause |
|---|---|
| Orders rejected by Qikink | A SKU on the store product that does not exist in your Qikink catalogue. |
| Wrong item printed | A variant mapped to the wrong SKU. Check size and colour mappings individually. |
| Nothing pushes | Sandbox credentials in live mode, or the push is gated on a payment status that never arrives. |
| Duplicate print jobs | A non-idempotent push retried by a webhook. |
| Printed but nobody paid | Pushing on order placement rather than on payment confirmation. |
If you do not have the website yet
Everything above assumes you already have a store to connect Qikink to. If you are still taking orders in DMs, that is the part worth fixing first — the integration is the easy half.
A SitesPlaced store is free to build and publish, with 0% commission on every sale, on every plan. Every integration on this page is included — you connect your own accounts and nobody takes a cut in the middle.
On SitesPlaced the push happens automatically on paid orders and is idempotent on the Qikink order id, so a retried webhook cannot print twice. Printify is included free too for US, UK and EU printing.
Frequently asked questions
What credentials does Qikink need?
A Client ID and a client secret, which are exchanged for an access token. Sandbox and live are separate environments with separate credentials and different hosts.
Do I upload artwork through the integration?
No, and you should not want to. Set each product up with its artwork in your Qikink dashboard, which gives you a SKU, and reference that SKU from your store. Print files staying with the printer is what makes it reliable.
When should an order be sent to Qikink?
On payment confirmation, never on order placement. Pushing on placement means an abandoned payment sends a real print job you get billed for.
Why was the wrong item printed?
Almost always a variant mapped to the wrong Qikink SKU. Check size and colour mappings individually — print-on-demand has no returns shelf to absorb the mistake.
Skip the integration work entirely
Build the store free, connect Qikink, map your SKUs. Paid orders print and ship themselves. 0% commission on every sale.
