Merch program management software is the system a company uses to run branded merchandise as an ongoing program. It holds the approved catalog, the storefronts people order from, the budgets and approvals that govern spend, the inventory, and the fulfillment, in one place. Buyers also search for it as swag management software, branded merchandise management software, or promotional products procurement software. If you run merch for a multi-location company, see Brandmerch for enterprise or request a demo.
What is merch program management software?
It is software that controls who can order which branded products, from which budget, with whose approval, and from which stock. Placing the order is a small part of the work. The software manages the controls around each order.
A complete platform covers six jobs:
- Catalog: the approved products, with approved logos in approved placements.
- Ordering: storefronts and carts for the people who need merch, across teams and locations.
- Budgets: a spend limit per team, brand or region, checked when the order is placed.
- Approvals: rules that send large or over-budget orders to a named person.
- Inventory: one count of what you own, wherever it sits.
- Fulfillment: storage, kitting and shipping that start from the order, with no handoff.
A tool that covers only one of these jobs is a store, a warehouse or a gifting tool rather than a program management platform.
What problem does it solve?
Most merch program problems appear after the purchase, in tracking spend, stock and brand use.
A common example: merch is stored in three offices, two online stores have no clear owner, and five people order on their own because it is faster than asking. In that situation, the company cannot easily answer basic questions. How much did events spend last quarter compared with onboarding? Which office has the medium hoodies? Did the regional team use the current logo? Is the stock in the warehouse still usable, or is it outdated and likely to be written off?
As a company grows, more people, locations and vendors are involved in merch, and tracking it by hand gets harder. The software replaces the spreadsheet, the inbox and one person's memory with rules that still apply when that person is out of the office.
How is it different from a gifting platform?
A gifting platform is built around a send. Merch program management software is built around a program. The two overlap, and buyers often evaluate one when they need the other.
Gifting platforms start with a recipient. A sales or marketing rep picks a person, picks a gift, and the platform ties the send back to a CRM record so the spend can be attributed to pipeline. Sendoso describes itself as a "Gifting & Direct Mail Platform." Reachdesk calls itself a solution for "Global Gifting & Swag." Both serve sales, marketing and customer teams well, and Sendoso also lists onboarding and recognition for people teams.
Merch program management starts with a catalog and a set of rules that persist. Recipients change often, while the catalog, budgets and approval rules stay in place. Onboarding, events, internal company stores, partner programs and client gifts all draw on the same catalog, budgets and stock.
| Question | Gifting platform | Merch program management |
|---|---|---|
| Unit of work | A send to one recipient | A program used by many teams |
| Main buyer | Sales and marketing | Marketing ops, HR, procurement, brand |
| Success measure | Pipeline attributed to sends | Spend control, brand consistency, stock accuracy |
| Who orders | Reps with seats | Anyone the program allows, often through a storefront |
| Core controls | Send tracking tied to CRM records | Budgets per team, approvals by order value, a locked catalog |
If your question is "which rep sent what to which account," you want a gifting tool. If your question is "who is allowed to order what, at what price, from which budget, and do we still have it in stock," you want program management. Many companies need both, so it helps when gifting runs inside the program and uses the same catalog, budgets and stock.
What features should merch management software have?
These capabilities distinguish a program management platform from a basic online store.
- Budgets checked at checkout: a report shows overspending only after it has happened. A budget control flags the order at checkout and holds it for approval. Look for budgets per team, brand or region, on your fiscal calendar, with the balance visible to the person spending it.
- Approvals that route by order value: if every order needs approval, people start ordering outside the process. Small orders should go straight through. Orders over a threshold, or over budget, should go to a named approver. Finance should be able to approve without needing a login.
- Brand control built into the catalog: the most reliable brand guideline is a catalog that only contains approved products, logos and placements. If a regional team can only order approved items, nobody has to check each order afterward.
- Proofs before production: every decorated item should be proofed and signed off before anything is made.
- One inventory count: stock in a warehouse, an office closet and a showroom is the same asset. It should appear in one view, with what is available, incoming and reserved.
- Fulfillment that starts from the order: if shipping depends on someone emailing a warehouse, orders wait whenever that person is busy.
- Spend reporting by team: what each team spent, on what, without manual spreadsheet work.
- Integrations: a CRM connection for gifting, and an API with webhooks for anything else.
How do you score merch management software vendors?
Score each vendor from 1 to 5 on the criteria below, multiply by the weight, and add the results. The weights suit a large, multi-location company. Adjust them to your program before the first demo, not after.
| Criterion | Weight | What a 5 looks like | Ask in the demo |
|---|---|---|---|
| Budgets and spend control | 15% | Budgets per team or brand on your fiscal year; over-budget orders held for approval | "Show me an order that goes over a team's quarterly budget." |
| Approval workflows | 15% | Approval by order value; finance can approve from email | "Who approves a $6,000 order, and what do they see?" |
| Org structure | 10% | Departments, regions or brands as groups, each seeing its own catalog | "How would you set up our twelve locations?" |
| Brand control | 10% | Locked catalog, approved artwork, proofs before production | "Can a regional manager upload a different logo?" |
| Inventory | 10% | One count across warehouse and office locations | "Show stock held in our office next to stock in your warehouse." |
| Fulfillment and kitting | 10% | Storage, kitting and shipping triggered by the order | "What happens between an order and a shipped box?" |
| Storefronts | 10% | Company-paid and employee-paid stores, with access controls | "Can one store be invite-only and another use a shared code?" |
| Catalog and reach | 5% | Hundreds of brands; international shipping | "How many brands, and which countries do you ship to?" |
| Reporting | 5% | Spend by month, group, person and product | "Show last quarter's spend by department." |
| Integrations and API | 5% | CRM integration, documented API, webhooks | "Can our CRM trigger a send from stock?" |
| Pricing clarity | 5% | Published plan prices; fees itemized | "What will we pay in year one, all in?" |
Ask every vendor to run the same scenario live, in their product, with your numbers. Score a feature you only see on a slide as a 1 until the vendor shows it working.
How should a 12-location company set up departments, budgets and approvals?
Start from how money is already managed, not from the software. Here is a typical setup for a company with twelve locations, three regional managers and a central marketing team.
- Structure: one company account. Three regional groups (West, Central, East), each holding four locations. Two functional groups for central teams: Marketing and People.
- Catalog: a core collection every location can see (tees, caps, drinkware, a welcome kit). A regional collection for local events. A leadership collection visible only to the people who need it.
- Budgets: a quarterly budget per region, counted from the fiscal start month. An annual budget for People, sized to hiring plans. Marketing on an annual budget that covers events.
- Approvals: orders within the region's budget go straight through. An order that would take a region over budget is held for a named approver, such as the head of marketing ops. Invoice orders over $1,000 go to accounts payable, who approve from an emailed link.
- Stock: core items held centrally and shipped to locations on request. Each location's small supply logged as its own stock location, so the count includes it.
- Reporting: one monthly view of spend by region and by product, sent to finance.
With this structure, headquarters no longer approves every routine order but still reviews large and over-budget ones. A location manager orders what they need. Approvers see only the orders that break a budget or cross the invoice threshold.
How should a multi-brand group set it up?
A group that owns several brands has different needs. It usually pays as one company but needs each brand to look like itself.
- Structure: one company account with one bill. Each brand is a group. Buyers are assigned to the brand they work for.
- Catalog and artwork: each brand sees its own collections and its own logo files. A buyer at one brand cannot order with another brand's mark.
- Budgets: an annual budget per brand, on the group's fiscal year. Over-budget orders are held for approval, not refused, so a buyer is never stuck at checkout.
- Shared stock: blank or group-branded items held once and shared across brands, so each brand does not reorder the same tote.
- Reporting: spend by brand, with shipping, tax and fees shown once for the group, so the brand totals add back up to the invoice.
The alternative, a separate account per brand, gives each brand control but loses the shared stock, the combined buying and the single view of spend. Most groups are better served by one account with brand-level groups.
How do company stores fit into a merch program?
A company store, or storefront, is how most people in the program will order. It is where people place orders, while the catalog, budgets, approvals and stock behind it make up the program.
Decide three things for each store:
- Who pays: the company pays, with prices shown or hidden, or the shopper pays. Some stores mix both: the company covers a welcome item and employees buy extras.
- Who gets in: a public link, a shared link and access code, or individual invitations.
- Who approves: no approval, approval on every order, or approval only above a dollar threshold.
A large company often runs several stores: an employee store, a store for each region's events, a partner store, and a client gift catalog. They should all draw on one program. If each store runs as a separate system, spend, stock and approvals are split across systems again. More on this on our company store page.
Where do common vendors sit?
Vendors in this space start from different places. The descriptions below come from each vendor's own website, checked in November 2026.
| Vendor | How it describes itself | Published pricing |
|---|---|---|
| Sendoso | "Gifting & Direct Mail Platform," with sales, marketing, customer and people use cases | Pricing not published; plans quoted by sales |
| Reachdesk | Gifting and swag platform for sales and marketing, with Salesforce and HubSpot integrations | "Plans start at $20,000/year"; $2,500 minimum order for swag sourcing |
| Swag Pro (Printfection) | "Swag management platform" with company swag stores, giveaways and fulfillment | Plan prices not published; shipping from $5.99/order and $25/month for items beyond 20 SKUs on Standard |
| SwagUp | Custom swag platform for packs, bulk orders, warehousing and swag shops | Membership tiers published, from a free Basic tier; Enterprise price not published |
| Brandmerch (MerchOS) | Merch program platform: storefronts, budgets and approvals, inventory, gift links and fulfillment | Procurement from $19.99/month; Business with storefronts from $199/month billed annually; Enterprise custom |
Use the scoring table, not the category label. Two vendors with the same label can differ widely on budgets, approvals and inventory. For a closer look at the gifting side, see Sendoso alternatives and the best swag management platforms.
What does merch program management software cost?
Software fees are usually a smaller part of the total cost than products, storage and shipping. Compare vendors on the full year.
- Platform fee: the subscription. Brandmerch's Procurement plan starts at $19.99 per month, the Business plan with storefronts starts at $199 per month billed annually, and Enterprise is priced to the program. There is no free plan.
- Product and decoration: what you pay per item, including setup charges.
- Storage: what it costs to hold stock, and how it is measured.
- Pick, pack and kitting: the per-order or per-item handling charge.
- Shipping: domestic and international, and whether it is passed through at cost.
- Minimums: any order minimum or annual commitment.
Ask each vendor to price the same year: your expected orders, kits and shipments. A low platform fee does not always mean a low total cost.
When have you outgrown the spreadsheet?
Companies often keep using a spreadsheet after it stops meeting their needs. Signs it is time to move to software:
- More than one person orders merch, and they do not always know what the others ordered.
- You hold stock in more than one place, and no single view shows all of it.
- Something off-brand shipped in the last year.
- You cannot say what each team spent on merch last quarter without an afternoon of work.
- A recurring process, such as onboarding kits or event shipments, depends on one person remembering.
- You have written off obsolete stock, or suspect you should.
If three or more of these apply, managing the program by spreadsheet likely costs more in staff time and unused stock than it appears.
How does Brandmerch handle merch program management?
Brandmerch runs on MerchOS, a platform for running merch programs across teams and locations. Brandmerch is vertically integrated: a marketplace, a warehouse and a gift packer in one company. Brandmerch sources, proofs, warehouses, kits and ships.
- Catalog: 575 brands, with private collections for your approved products and a brand library for your artwork. You can also transfer your current vendors and items into Brandmerch and manage them in the same place.
- Groups: on Enterprise, name your groups after how you work (regions, departments or brands). Buyers see the collections and artwork for their group, and every order is tagged to one group.
- Budgets: annual or quarterly budgets per group, counted from your fiscal start month. An order that would break a budget is flagged at checkout and held for approval.
- Approvals: named approvers, and owners or managers if you allow it, approve in the dashboard. Accounts payable can approve from an emailed link without a login, and can be set to review only invoices above a dollar threshold.
- Storefronts: company stores, gift catalogs, event pop-ups and pre-order campaigns that collect orders before production. Company-paid or employee-paid, with public, access-code or invite-only entry, and approval on every order or only above a threshold.
- Stockroom: one inventory across the Brandmerch warehouse and your own locations, such as an office or showroom, showing what is available, incoming and reserved.
- Gift links: send a link and the recipient chooses the item and size and enters their own address.
- Integrations: Salesforce through Salesforce Flow and a published recipe, a native HubSpot app with a gift workflow action (in early access), and a documented REST API with webhooks. Brandmerch also connects to HR systems, so a new hire can trigger a welcome kit without anyone opening a store. See CRM gifting.
- Reporting: spend by month, by group, by person and by product.
- Shipping: to 220 countries.
Changent uses this setup to run merch for a network of around 280 partner organizations: one catalog, budgets checked at checkout, approval above a set order value, and inventory in one stockroom. Read the Changent case study, or see how it fits large organizations on the enterprise solutions page.
Buyer's checklist: how to run the evaluation
- Write down your structure. List locations, departments or brands, who orders today, and who approves.
- Set budgets and thresholds on paper. Decide the budget per group, the fiscal start month, and the order value that needs approval.
- Count your stock. List every place merch sits today, including office closets.
- Weight the scoring table. Agree the weights with finance and brand before the first demo.
- Run the same scenario with every vendor. An over-budget order from a regional manager, approved by finance, shipped from stock.
- Price a full year. Platform fee, products, storage, handling and shipping, on your volumes.
- Check the references. Ask to speak with a customer whose structure resembles yours.
- Start with one program. Move onboarding kits or one region first, then add the rest.
For the operating side of a program, read our guide to managing merch across teams and the enterprise swag program guide. To see MerchOS set up for your locations, budgets and approvals, request a demo, explore MerchOS, or review pricing.
