Connecting Print-on-Demand Production to a Shoplazza Store | PrintDoors

Shoplazza print on demand stores are often built for markets outside the United States, which changes the questions an integration has to answer. Currency, storefront language, regional shipping rules and the production region that will fulfil each order all interact, and a setup that works for a domestic store can produce delivery estimates that are wrong for half the customer base. This guide covers what the connection handles, what the merchant still owns, and the settings worth checking before the store goes live.

What does Shoplazza print on demand integration cover today?

Order routing and fulfilment status, plus catalogue import.

The connection carries products from the supplier catalogue into the store, routes paid orders to production, and returns tracking and fulfilment status so the standard customer notification can be sent.

Three functions sit inside the integration. Catalogue import brings product data, including variant options, into the store so listings are built from real producible combinations rather than invented ones. Order routing transmits the paid order with its variant, artwork and shipping address to the production system, which converts it into a production job. Fulfilment write-back returns the dispatch status and tracking number to the store order. Everything else — pricing, theme, collections, discounts, tax settings and marketing — remains a Shoplazza responsibility. That division is deliberate and worth understanding before setup: the supplier is accountable for producing and dispatching the item the store sold, not for how the store presented or priced it. PrintDoors connects to Shoplazza by API alongside Shopify, Etsy and WooCommerce, and documents Shoplazza and BigCommerce topics in its help centre.

What does the store and account need before you connect?

Four prerequisites, all checked in advance.

An admin-level Shoplazza account to authorise the connection, a supplier account in good standing, a defined shipping configuration for your main markets, and a product list you are willing to rebuild from the supplier’s variant matrix.

The fourth item is the one that causes most rework. Merchants who create listings first and connect afterwards often discover that the size run, colour set or product variant they published is not producible, and correcting it means editing live listings. Import the supplier’s catalogue first, build the Shoplazza product from the imported variants, and only then add pricing and descriptions. Two other checks repay the time: confirm which production region will serve each market you sell into, since that decides your delivery estimates, and confirm the currency you will price in, because the supplier quotes in one currency while the storefront may display another. Payment processing costs follow the rate card of your provider; published structures such as Stripe pricing and the requirements of the PCI Security Standards Council are the reference points for building a pricing floor.

Connecting products and syncing variants

Variant mapping is the heart of the setup and the source of most failures. A single garment can span eight sizes and a dozen colours, and only some of those combinations exist. If the store offers a combination the supplier does not produce, the order is accepted and then stalls, which costs a customer message and a manual correction. The reliable method is to import the supplier’s available matrix and generate the store’s options from it, so a non-existent combination has no way to reach checkout. Once variants are mapped, mockups should be generated per variant from the real product template rather than reused across colours, because the garment colour changes how a design reads and a mismatched mockup is a return waiting to happen. PrintDoors supports CSV design and order import templates, which allows a multi-variant catalogue to be prepared in bulk and keeps the mapping list consistent as products are added.

How does an order route from checkout to production?

The order leaves the store once it is paid and eligible.

Checkout completes, the store records the payment, the integration transmits the line items and shipping details to production, and the job is scheduled against the applicable dispatch window.

Three things can interrupt that path, and all three are diagnosable. An order that is not yet in an eligible status will queue rather than fail, so an order that appears missing is often simply not ready. A variant that does not map cannot be converted into a job at all, which is why the mapping step matters. Artwork that does not match the product template will pass the routing step and fail at production review, producing a message rather than a job. Because the pipeline is asynchronous, the two states worth monitoring are “paid but not yet a job” and “job complete but no tracking”. PrintDoors exposes order and logistics tracking inside the seller account so both states are visible without checking two systems.

Tracking and delivery notifications

The store sends the notification; production supplies the data. Once the tracking number is written back to the order, the store’s standard shipping confirmation goes out, provided notification settings are enabled. Two timing decisions make that notification useful rather than confusing. Tracking should be written at dispatch rather than at order acceptance, so the delivery estimate begins when the parcel exists. And the delivery estimate shown to the customer should reflect the production region that fulfilled the order, not the store’s average. On international shipments, carriers frequently hand the parcel to a local operator for final delivery, which means a single tracking number may stop updating before the parcel arrives; telling customers that in the shipping policy prevents a support ticket even when nothing has gone wrong.

Regional storefronts, currencies and shipping rules

Regional storefronts multiply the variables that a single production route has to satisfy. Each market you serve brings its own currency, its own delivery expectation and its own import treatment, and a shipping rule priced for one market usually produces a loss in another. Structure the shipping configuration around markets rather than around a single worldwide rate: one rule per market or region, priced from the packed weight of the products you sell there and from the applicable production region. Recheck the free-shipping threshold, if you use one, against the heaviest product in the catalogue rather than the average, because bulky items such as bedding sets and blankets are what break a flat threshold. Carrier rate structures are published openly for reference — see the FedEx international shipping and UPS international shipping documentation — and are useful for sanity-checking a quoted rate before publishing it.

What are realistic transit times by fulfilment location?

Transit time is set by where the parcel is produced, not by where the supplier is headquartered.

PrintDoors operates production and fulfilment across these seven regions, which is what makes a market-based shipping structure practical rather than theoretical. Confirm the dispatch window that applies to the specific product as well as the region: PrintDoors publishes four-hour production with twenty-four to seventy-two hour dispatch across more than 140 products, with a stated compensation rule when the window is missed, while other products follow standard production scheduling.

Handling returns and production failures

The customer’s contract is with the store, so the store resolves the issue and the supplier claim runs behind it. Publish a policy that states what is covered, what evidence a claim needs and what remedy applies: defective or misprinted items are replaced, personalised items are not returnable for change of mind, and sizing requests are handled according to the store’s own terms. Then align that policy with the supplier’s rules so the two do not contradict each other in public. PrintDoors maintains a refund policy that separates production faults from sizing and preference issues, and order-specific claims are handled through support@printdoors.com. Keeping the claim path separate from the customer conversation is what allows a store to respond quickly without committing to a remedy the supplier has not agreed.

Setup walkthrough with the settings that matter

Work through the sequence in order; each step depends on the previous one.

1. Open a supplier account and confirm the production regions that serve your target markets.
2. Import the catalogue so variants come from real producible combinations.
3. Build Shoplazza products from the imported variants, then add pricing and descriptions.
4. Authorise the store connection from the admin account and confirm the link is active.
5. Map each live product to its supplier product and record the mapping list.
6. Generate mockups per variant from the real product template.
7. Configure shipping rules per market, priced from packed weight and the applicable production region.
8. Set dispatch and delivery expectations from the published supplier window for each product.
9. Enable fulfilment notifications and confirm tracking is written back at dispatch.
10. Publish the refund, replacement and duties policies.

Checklist before switching the store to live

Run the following before any marketing spend, and keep the answers where a colleague can find them.

• Every live variant maps to a producible combination.
• No product on sale in a market you cannot fulfil at a rate you can support.
• Shipping rules priced per market, including the heaviest item in the catalogue.
• Delivery estimates consistent between the product page, the shipping policy and the production region.
• Duties and import charge responsibility stated for cross-border orders.
• Refund and replacement policy published, with personalised-item exclusions.
• One test order placed through the store and followed to delivery, including the notification.

Product identification and retail barcode requirements are worth confirming where a marketplace or wholesale channel demands them; the GS1 barcode standards are the reference point for retail identification, and Shoplazza’s own documentation and help centre at Shoplazza Help Center cover store-side configuration.

Conclusion

A Shoplazza integration is a routing layer, and its reliability is decided by four merchant-owned settings: variant mapping, mockup accuracy, market-based shipping rules and a delivery estimate that matches the production region. The connection itself takes minutes; the configuration is what determines whether the store runs without intervention. Set the catalogue up from the supplier’s real variant matrix, price shipping market by market, and publish a policy that matches what production can actually deliver. After that, the integration should be invisible.