Start with a migration brief, not a catalogue import
The storefront can stay open while a new production route is tested. What needs to be controlled is which supplier owns each order, what the customer will receive and what happens if the test fails.
Assign one person to own the migration and one person to check order exceptions. Write down the reason for moving: product fit, unreliable fulfilment, a specialist technique or better delivered contribution. That reason becomes your acceptance criterion.
Record the starting point
- Current product and variant IDs, supplier IDs and artwork versions.
- Blank model, fibre composition, fabric weight, fit and size chart.
- Retail price, actual order costs and the delivery promise shown at checkout.
- Print positions, dimensions, branding and product photographs.
- Open orders, cancellations, refunds and returns still owned by the old supplier.
Keep this record as the rollback reference. Use the supplier selection checklist if the replacement has not yet been validated.
Stage 1: select the products worth proving first
A hero SKU is a product that matters commercially: a bestseller, a recurring purchase or a garment central to your brand. Pick one to three for the first test. Include a difficult design or dark variant if it represents real customer demand.
A quiet, easy product can make an integration look reliable without testing the cases that hurt your business. Conversely, moving the whole long tail creates too many variables to diagnose at once.
| Candidate | Why test it? | Move when |
|---|---|---|
| Main bestseller | Tests the product most customers will see. | Quality, route and contribution pass. |
| Dark or demanding artwork variant | Exposes print and file-preparation issues. | The difficult design is approved physically. |
| Typical two-item basket | Tests parcel splitting and additional-item costs. | Tracking and total cost match the promise. |
| Low-volume long tail | Adds mapping work without proving the core route. | The first batches are stable. |
Stage 2: match the garment before mapping its name
Two “premium cotton tees” can have different shoulder widths, lengths, fabric weights and necklines. A supplier switch can therefore become an unannounced product change.
Create an equivalence sheet
For each hero product, compare composition by colour, fabric weight, cut, measurements, tolerances, size range, care instructions and printable areas. Mark each field as matched, different or unverified. Do not treat an unverified field as a match.
Where the replacement differs, update the size chart, copy and imagery before moving customer orders. If the change alters the product substantially, a separate listing or clearly described product revision may be the better choice.
For cotton AOP, compare the cut-and-sew pattern as well as the fibre content. Our cotton AOP guide explains why full-surface printing brings its own seam and hand-feel checks.
Stage 3: rebuild artwork for the new print area
Copying the old supplier’s preview is not artwork migration. Use the replacement product’s current template and rebuild the file at the intended physical print dimensions.
- Check resolution at the final print size, not just the image’s pixel count.
- Set the required colour profile, file format and transparency rules.
- Confirm front, back and sleeve placements separately.
- For AOP, cover panel bleed and keep critical details inside safe zones.
- Save a versioned file and approval image for each migrated product.
A graphic that measures 25 cm on the old sample should be measured on the replacement too. Similar proportions in two mock-ups do not prove identical print placement.
Use Snapwear’s DTG artwork guidance or the exact AOP product instructions. Requirements vary by technique and item.
Stage 4: approve light and dark samples, then wash-test them
For a DTG garment sold in both light and dark colours, test both with artwork you actually sell. For AOP, test the intended fabric and include demanding coverage or panel transitions.
Photograph the samples in consistent light. Record print dimensions and location, garment measurements, colour, fine detail, hand feel and packaging. Compare them with an approved example from the old route.
Use the care label as the test rule
Measure and photograph the garment before washing. Repeat the inspection after a wash and after several care-label cycles; five cycles can be a useful screening test if appropriate to the item. Record shrinkage, twisting and visible print changes. This is a screening process, not a lifetime durability certification.
Order at least one repeat of the hero SKU before scaling it. A single good sample shows the product can meet your standard; it does not establish consistency.
Stage 5: validate fulfilment in the markets you serve
Test an address in the UK, an EU destination and a US destination if all three are part of your sales plan. If a market is outside the launch scope, keep it out of the initial rollout rather than assuming a test elsewhere covers it.
| Record | What it resolves |
|---|---|
| Production origin and method | Whether this SKU uses the route you expected. |
| Approval, dispatch, first scan and delivery times | Production time versus carrier transit. |
| Full checkout and delivery charges | Shipping, conversion and any border-related costs. |
| Parcel count and tracking | Split shipments and customer notification behaviour. |
| Product and packaging on arrival | Whether the destination sample matches your approved standard. |
| Support and return route | Who handles the exception and what it costs. |
Check normal and peak estimates separately. A few test parcels cannot establish a reliable delivery percentile, but they can expose a wrong dispatch origin, an extra charge or a missing tracking event.
Snapwear’s public pages describe different product availability and technologies by location. Do not promise identical catalogues or production methods in every hub. Use the shipping rates and delivery planning guide, then confirm the actual route with the team.
Stage 6: map each storefront variant to one production variant
A SKU code, a storefront variant ID and a supplier variant ID are different identifiers. Map them explicitly. Do not rely on colour names or size labels alone.
| Store variant ID | Merchant SKU | Old supplier ID | New supplier ID | Artwork version | Status |
|---|---|---|---|---|---|
| Store ID A | HERO-BLACK-M | Old ID A | New ID A | hero-v2-front | Sample approved; routing test pending |
| Store ID B | HERO-WHITE-M | Old ID B | New ID B | hero-v2-front-light | Not yet approved |
Test the complete order cycle
- Paid order import, correct product, size, colour and artwork.
- Tracking returned to the right storefront order and parcel.
- Stock or unavailable-variant handling.
- A cancellation request and the point after which production cannot be stopped.
- An address correction within the supported workflow.
- A mixed basket and any separate customer notifications.
Preserve listing URLs and existing variant IDs where the platform supports remapping. Check each connector’s actual behaviour; this guide does not promise a one-click import from another supplier. See Snapwear’s documented integrations.
Stage 7: run both setups without duplicating orders
A parallel run means keeping both production routes available while selected orders use the replacement. It does not mean sending the same live order to both.
- Choose the exact variants and order group included in the trial.
- Assign one production owner to each order. Check overlapping auto-import rules.
- Reconcile storefront order IDs, supplier acknowledgements and tracking daily.
- Keep a list of open orders that remain with the old provider.
- Define the stop rule before starting: for example, a mapping error, unexpected product substitution or a failed delivery-cost assumption.
Make rollback a routing decision
If the trial fails, stop sending new affected orders to the replacement route. Reconcile orders already accepted for production before routing anything again. Confirm cancellations explicitly; an order disappearing from one dashboard does not prove the factory has stopped it.
Give customer support the new size information, dispatch origins and exception process before the trial starts. Customer questions should not be the first place an operational change is discovered.
Stage 8: move bestsellers first, then the long tail
Review each test batch against written thresholds for product quality, delivery, delivered contribution and integration errors. Set those thresholds from your own customer promise and economics; there is no universal defect rate that suits every brand.
Once the first hero products pass, move the next small group. Check every newly added product type and route. A successful DTG tee test does not validate an AOP hoodie or a mug.
Move low-volume products later. Some may remain with the old provider if there is no suitable replacement. Keep responsibility for old orders, returns and replacements clear until that work is finished.
If your current provider is Printful, the Printful alternative UK comparison can help decide which products are worth trialling with Snapwear.
One-page migration checklist: copy it into your launch brief
Use this as the approval record for the first product. A downloadable checklist is not currently offered on this page.
- Hero SKU and migration owner named.
- Old product, artwork and routing record saved.
- Physical specification differences documented.
- New template and artwork version approved.
- Light/dark or relevant coverage samples approved.
- Care-label wash check and repeat sample reviewed.
- Relevant UK, EU and US routes tested; costs recorded.
- Every live variant mapped and test order completed.
- One production owner assigned to each order.
- Trial batch, stop rules and rollback route defined.
- Store copy, imagery, delivery information and support brief updated.
- Bestseller rollout approved; long-tail products scheduled separately.
For your internal worksheet, add “Owner”, “Evidence link”, “Pass/hold” and “Approval date” beside each item. A future PDF could use this checklist; no download link or email capture is implied.
FAQ
Switching POD suppliers: common questions
Do I need to move my whole catalogue at once?
No. Start with one or a few hero products, then expand after product, route and integration checks pass. Low-volume products can move later or stay with the old provider if there is no suitable replacement.
Can the storefront stay open during migration?
A staged migration can keep the store open while selected products are tested. Every live order needs one production owner, and unsupported or unapproved variants must not be routed to the replacement.
Will the replacement garment be identical?
Do not assume so. Compare composition, weight, fit, measurements, tolerances, print area and care instructions. Update the listing and imagery if the physical product changes.
Can I reuse the old print files?
Only after checking them against the new product’s current template, physical print size, resolution, colour profile and transparency rules. AOP panels and safe zones may require artwork rebuilding.
How long does a supplier migration take?
The duration depends on sample production and delivery, wash checks, artwork changes, integrations and the number of products and markets. Use evidence gates rather than promising a fixed number of days.
What is the most important rule during a parallel run?
Each order must have one production owner. Reconcile accepted orders before rerouting or cancelling anything so the same customer order is not produced twice.
Is there a downloadable migration checklist?
Not currently on this page. The checklist above is available to copy into your own launch brief; no PDF download or lead-magnet delivery is being promised.
Sources and verification notes
This is a recommended operational framework, not a guarantee of uninterrupted sales or identical replacement products. The checklist and test gates are editorial guidance; they do not describe an automated migration service.
Snapwear capability statements were checked against official public pages on 12 October 2026. Confirm live connector behaviour, product availability, cancellation rules and production routing for your account before importing customer orders. No migration or sample orders were placed as part of writing this guide.