Promotional products: planning a merchandise tool

What to take away

Why implementation stalls

Most promotional merchandise tool projects fail on process, not software. Teams load a partial catalogue, then keep quoting in spreadsheets because the tool cannot match a decoration price to a garment colour.

The fix is to map the workflow before you shop. Write down every step from enquiry to delivery, including who approves artwork and who signs off the invoice.

Once you have mapped the workflow, use the promotional merchandise supplier comparison as optional further reading when shortlisting vendors.

Scope the workflow first

Start with the order types you handle. A single-colour logo on a mug behaves differently from multi-position embroidery on a jacket. Each type needs its own fields for quantity breaks, setup charges and lead times.

List your five most common order types and the fields each one needs. Anything the tool cannot store, your team will track elsewhere.

Set a realistic go-live date. Allow two weeks for data migration and two for testing on live quotes.

Decide buy or build

Off-the-shelf tools win when your process resembles the industry standard: quote, approve artwork, order stock, decorate, dispatch. Configuration covers most differences. The table below gives examples, but its pricing notes describe pricing models rather than comparable GBP costs; request current quotes before making a buying decision.

Build only pays if you hold unusual stock arrangements or bill through a system no vendor integrates with. Salesforce Sales Cloud starts at $25 per user per month for Starter Suite, but needs custom objects and integration work. Zoho CRM starts at £14 per user per month, but needs custom modules for decoration pricing. These generic CRM prices are not a like-for-like cost comparison of merchandise platforms.

For optional wider reading after you have worked through the implementation steps, see the promotional merchandise tools and supplier guide for 2027.

Test data before go-live

Data quality decides whether the tool earns its keep. Supplier price files arrive in different formats, and product codes rarely match across vendors.

Run 50 sample products through the tool and check the quoted price against a manual calculation. Fix the mapping rules before you load the full catalogue.

Imported goods add another layer. Any product sourced from outside the UK needs the right classification, so check the commodity codes guidance on GOV.UK when you set up product records.

Build compliance into the tool

Merchandise carries duties a generic sales tool will not flag. For electrical products within scope placed on the Great Britain market, check the Electrical Equipment (Safety) Regulations 2016 and the applicable UKCA or CE marking requirements. HSE guidance on maintaining portable electrical equipment is relevant to workplace equipment; PAT testing is not a substitute for product-safety compliance.

Store test dates and responsible owners against each electrical product record. That turns a paper chase into a report. For product-safety enforcement guidance, contact the relevant local authority Trading Standards service.

For UK advertising claims about merchandise, check the CAP Code, administered by the Advertising Standards Authority (ASA). Claims must not mislead and should be substantiated; a social platform's advertising guide covers ad formats and targeting, not the rules for advertising claims.

Run a pilot campaign

Pick one product line and one client for the first live run. Keep the spreadsheet running in parallel for that order only.

Compare time spent per quote before and after. If the tool adds steps, the configuration is wrong, not the tool.

Train two people, not one. Cover for holidays and illness from day one.

Glossary

Common questions

How long does implementation take?

For a mid-size catalogue, allow 6 to 10 weeks including data migration and pilot testing. Rushing the data stage is the most common cause of delay later.

Should we buy a platform or build one?

Buy unless your order flow genuinely differs from the standard quote-to-delivery path. A custom build adds maintenance costs that rarely show up in the initial quote.

What data should we clean first?

Supplier price lists, product codes and decoration costs. These three fields drive most quoting errors, so test them on a sample before loading everything.