Help › Troubleshooting

Troubleshooting

The handful of things that trip merchants up most — and exactly how to fix each one.

The builder isn't showing on my storefront

Work through these in order. The first one applies to both editions and is by far the most common.

1

The builder isn't enabled

A builder only renders once it's switched on for your shop — in Initial setup in the Shopify app, or under Config in the PrintKit portal. If the spot on your page is empty, the builder is almost always still off. An enabled builder also has to be covered by your current plan.

Shopify app

2

The block isn't added, or is on the wrong template

In Online Store → Themes → Customize, confirm the Product Builder app block (Add block / Add section → Apps) is actually on the page you're viewing, that its Builder dropdown is set to the right one, and that you clicked Save. A block added to one product template won't appear on a different one.

3

The app-proxy path was changed

The builder loads through the app proxy at /apps/presskit/…. If you (or the block's Advanced “App proxy path” setting) changed that path, the builder can't load. Leave it at the default /apps/presskit unless you deliberately customized the proxy subpath. The direct link form is /apps/presskit/embed/<builder>.

Any website

2

Your platform stripped the script tag

Wix, Square Online and GoDaddy sandbox scripts inside their page editors, so a plain <script> tag silently does nothing. Use the iframe variant of your snippet instead — it's shown in your dashboard next to the one-liner — and give it a height of around 1000 px.

Some builders also need the right block type: a Custom HTML block on WordPress, an Embed HTML widget on Wix, a Code block set to HTML on Squarespace, an HTML Embed element on Webflow.

3

You're looking at a preview, not the published site

Webflow's HTML Embed only runs on the published site, and won't execute on the free staging domain. Publish, then check the live URL. Several other builders behave the same way in preview mode.

4

A strict Content-Security-Policy is blocking it

Most sites don't set a custom CSP and need no change. If yours does, allowlist app.printkit.tech in both frame-src and script-src so the loader and its frame are allowed to load.

5

The key in the snippet isn't yours

The snippet carries your publishable key. If you copied an example from documentation rather than your own dashboard, or you rotated your storefront key after pasting, the builder won't load. Copy the snippet fresh from your dashboard — and if you rotated the key, re-paste it everywhere you use it.

Stickers: the wrong order type shows, or the switch is missing

The sticker builder can show packed sheets and rolls, single stickers, or a switch between them. If a page isn't showing what you expect:

Locking a page never turns a mode off. If singles disappeared everywhere, someone unchecked it in setup — that's a shop-wide switch. A page-level lock only hides the switcher on that one page. See the sticker guide.

Images are flagged as too small (DPI warnings)

The resolution meter warns when art is small for the print size it's placed at. It is a guide, not a gate — the shopper can always order — but here's how to get a sharp print:

Green means good for the chosen size, amber means it may look soft, and low art is flagged — but none of these block checkout. In the sheet and layout builders the shopper is asked to confirm before adding low-res art; they can still proceed.

A customer says the price they paid is different from what they saw

The price a shopper is shown and the price they are charged come from the same saved configuration, and PrintKit computes the final number on its own server — the builder can't send its own price. So the two cannot silently disagree. If a customer reports a difference, it's almost always one of these, all of which are expected:

What can't happen is a shopper editing the price downward: the server recomputes and has the final say.

My garment photo looks wrong in the builder

It still has its background

Use the Remove background button next to the uploaded photo, check the before/after preview, and choose Apply background removed. Your original is kept either way. If you get “too many background removals — please wait a minute and try again”, you've hit the rate limit — wait a minute and carry on. Photos must be PNG, JPG or WEBP and under 8 MB.

The generated colors came out wrong Shopify app

Almost always the source photo. One photo → every colour works by tinting the fabric, and tinting can only darken — so it needs a white garment to start from. A grey, cream or already-colored shirt will produce muddy results, and PrintKit warns you when the source doesn't look white. Re-shoot on a white blank, or reject the bad tiles and upload your own photos for those colors. Rejecting a tile changes nothing — that color simply keeps the stock photo.

The print box sits in the wrong place on my photo

Shopify app After uploading your own garment photo, use the Position Chest, Position Chest Pocket and Position Back buttons on that photo to drag each zone where it belongs. Chest and pocket are positioned on the front photo, back on the back photo.

Any website Open Config → Full Color Apparel Builder → Garment images and use that photo's row: the Chest, Chest pocket and Back buttons open the same drag-and-resize box, with a Set badge once a zone is positioned and a reset arrow to go back to the built-in placement. Same front/back rule — chest and pocket on the front photo, back on the back photo. Email support@printkit.tech if it still looks off.

Any website Re-saving Garment images used to wipe your print-area calibrations. That's fixed. If you calibrated print areas before 24 July 2026 and they later looked wrong, re-check them once — they will now survive future saves.

Saved shopper designs are kept for the retention window you chose in setup — 7, 30 or 90 days — and an automated purge deletes them after that. A link that no longer opens has passed its window, and a purged design can't be recovered.

Longer retention keeps more shopper personal data on hand for longer — pick the shortest window that still fits how your customers reorder.

The block shows but the builder area is empty

Same root cause as “not showing”: the block or snippet loaded, but the builder it points to isn't enabled (or isn't covered by your plan). Enable it, make sure the block's Builder dropdown — or the snippet's data-builder value — matches, and reload.

I can't get into my portal

Any website Use Forgot password on the login page. The emailed link is single-use and expires after 30 minutes, so request a fresh one if it's been sitting in your inbox. Only verified accounts receive a link — if you never confirmed your signup email, request a new confirmation instead. There's a limit of a few reset requests an hour; if you've hammered it, wait and try again, or email support@printkit.tech.