How to design a corporate merch system — beyond a product catalogue

Why a system, not just a catalogue

The most common mistake in Mexican corporate merch programs is treating the catalogue as the system. The catalogue is the list of products available — polos, tumblers, notebooks, backpacks. The system is everything else: how orders are approved, how deposits are paid, how production is tracked, how invoices are issued under CFDI 4.0, how ROI per event is measured, how the year closes with a report that procurement can take to the steering committee.

When the system does not exist, the program ends up depending on whichever supplier happens to be in place. Switching suppliers means rewriting the approval flow, redoing the quote templates, re-validating certifications and renegotiating payment terms. Procurement ends up running the program instead of marketing or HR running it.

A well-designed system operates in four layers. The first is catalogue and supplier layer: master SKU with MOQ, lead time, unit cost, monthly capacity and active certifications. The second is operations: ordering portal with approval workflow by amount and event type, integration with SAT for CFDI 4.0, ERP connection for budget commitment. The third is logistics: warehouse in Mexico City, Monterrey or Guadalajara with cross-docking or consolidation depending on the event calendar. The fourth is measurement: operational KPIs (delivery time, defect rate, rework) and business KPIs (cost per event, cost per employee, participation per program).

Corp-Merch.MX operates on this architecture for the fourth year running. The master catalogue carries 480 active SKUs, the supplier network adds up to 14 audited workshops, and the ordering portal processes between 80 and 120 requests per month. Invoices are issued under CFDI 4.0 from day one, with 16 % VAT breakdown or exemption depending on the tax regime, and per-lot traceability is archived for five years.

Before designing the system, three documents need to be on the table: the client's brand manual, the order history of the last twelve months (even if it lives in Excel), and the list of events or programs to be operated in the next year. Without these three inputs, the system is designed in the air and ends up being rewritten every quarter.

The system is not an IT project. It is an operations project with IT components. Conflating the two leads to over-investing in technology and under-investing in operations. The best ordering portal in the world fails if the approval flow is unclear or if the warehouse has no reception criteria.

Common mistakes that cost money and time

The first mistake is starting with the technology. A portal is bought or built before the master catalogue and the approval flow are defined. The portal is expensive, nobody uses it, and within three months it is replaced by WhatsApp. Technology comes at the end, not at the beginning.

The second mistake is treating the system as a public e-commerce catalogue. Corporate merch is not an open online shop. It is a closed system with authenticated users, pre-assigned budgets and scheduled events. Modelling it like e-commerce leads to spending on features nobody needs and skipping the ones that matter.

The third mistake is not involving finance from day one. Without the finance team, the CFDI 4.0 flow, VAT retentions when applicable and budget commitment do not close properly. A poorly issued invoice ends up in SAT review and the program gets cancelled.

The fourth mistake is underestimating the cost of changing supplier. When the primary supplier closes or changes terms, the system collapses because every file, format and timing is coupled to that supplier. A healthy system keeps files and processes portable.

The fifth mistake is not documenting decisions. The system works as long as the current owner stays at the company. When they leave, the knowledge leaves with them and the next owner starts from zero. Documentation is the continuity insurance.