SaasyLlama Docs

Appearance

Troubleshooting ​

Common issues with the Gang Sheet Builder and how to resolve them.

The "Create Gang Sheet" button doesn't appear ​

Cause: The button code's product handle check doesn't match your product.

Steps to resolve:

  1. In Shopify admin, go to your gang sheet product and check the handle (the URL slug at the bottom of the product page, e.g. custom-dtf-gang-sheet).
  2. In your theme's Custom Liquid block, find the line {% if product.handle == '...' %} and update it to match your product handle exactly.
  3. Save and re-publish the theme.

The builder opens but shows the wrong sheet size ​

Cause: The size parameter isn't being passed correctly from the button script.

Steps to resolve:

  1. Select a size variant on the product page.
  2. Right-click → Inspect on the size dropdown to check the option text format.
  3. Confirm the button script formats the size as 22x48 (digits only, x separator, no spaces or ").
  4. Check the URL in the browser tab when the builder opens — it should show ?size=22x48.

Images don't upload / "Add to Cart" fails ​

Cause: The backend is not running or is unreachable.

Steps to resolve:

  1. Visit https://your-backend-url.com/health — it should return {"status":"ok"}. If it times out or errors, your backend is down.
  2. Check your Railway/Render dashboard for errors or restarts.
  3. Open browser DevTools (F12 → Network tab) and click "Save & Add to Cart." Look for a failed POST /api/upload-gang-sheet request and check the error details.
  4. Verify VITE_API_URL in your frontend environment points to the correct backend URL and rebuild.

Cart addition works but no email is received ​

Cause: Webhook not configured, backend email environment variables missing, or webhook not reaching the backend.

Steps to resolve:

  1. Confirm the webhook exists in Shopify Admin → Settings → Notifications → Webhooks.
  2. Click Send test notification and check your Railway logs to see if the webhook arrived.
  3. If the webhook arrives but no email is sent, check EMAIL_USER, EMAIL_PASS, and OWNER_EMAIL environment variables on your backend.
  4. For Gmail, ensure you're using an App Password, not your regular account password.
  5. Check Railway logs for email-related errors (emailService.js).

Cause: The backend went down after the file was uploaded, or the file was deleted.

Steps to resolve:

  1. Confirm the backend is running at https://your-backend-url.com/health.
  2. Open the admin dashboard (/admin) and find the order. Try the download link from there directly.
  3. Check the uploads/ directory on your server to confirm the file exists.
  4. If the file is missing, the order may need to be reprinted from a new gang sheet — contact the customer.

DPI badge shows red on a customer's image ​

Cause: The image's pixel resolution is too low for the print size it's been scaled to.

What to tell the customer:

  • Red DPI means the image may print blurry or pixelated.
  • They should reduce the print size of that image (drag the corner handle to shrink it) until the DPI badge turns green.
  • Alternatively, they can use a higher-resolution version of the same artwork.

Auto-Nest doesn't seem to pack images tightly enough ​

Cause: The spacing setting is too large, or some images have transparent padding that inflates their bounding box.

Steps to resolve:

  1. Reduce the Spacing value in the Auto-Nest section (try 0.125").
  2. If images have large transparent borders in the original PNG, crop those out before uploading.
  3. Manually arrange images after Auto-Nest for any that can be packed more tightly.

The builder is slow or unresponsive with many large images ​

Cause: Very large source files (high-res PNGs) or too many images on the canvas strain the browser's canvas rendering.

Steps to resolve:

  1. Compress images before uploading. For DTF printing, 300 DPI at the intended print size is sufficient — there's no benefit to 600+ DPI source files.
  2. Use the Layers panel to temporarily hide images you're not actively working on.
  3. Close other browser tabs to free memory.

Still having issues? ​

Email support@saasyllama.com with:

  • Your shop domain (.myshopify.com)
  • A description of the issue
  • Any error messages from the browser console (F12 → Console tab)
  • Your backend URL and Railway dashboard screenshot (if relevant)

We typically respond within one business day.

SaasyLlama — Niche Apps. Built Different.

© 2026 SaasyLlama. All rights reserved.