How to choose trade program software

If you sell to the trade, you already run a trade program—whether or not you'd call it that. Someone applies, someone decides, someone sets up the account, and someone keeps the paperwork current. The only question is how much of that is a person's job.

The software category that automates it is young enough that the terminology hasn't settled. Products describe themselves as trade portals, B2B onboarding, wholesale account management, or tax exemption tools, and the overlap between them is uneven. Two tools that look interchangeable on a feature grid can differ enormously in whether they actually carry your compliance risk.

This guide is the evaluation framework we'd want a brand to use on any vendor in the category, including us. The Credenza-specific section is at the end and labeled, so you can read the rest as neutral guidance.

Trade program software automates the lifecycle between a designer discovering your brand and that designer placing tax-exempt orders at trade pricing. That lifecycle has seven stages, and most tools cover some but not all of them:

1. Intake—the application itself, and what you ask for.
2. Verification—establishing that the applicant is a practicing trade professional.
3. Decision—approve, decline, or route for review, against criteria you set.
4. Tax documentation—obtaining a valid resale certificate for the relevant jurisdictions.
5. Provisioning—creating the account in your commerce platform with the correct pricing and tax treatment.
6. Maintenance—renewals, expirations, revocations, and changes to the designer's details.
7. Intelligence—knowing which accounts are active, dormant, or worth calling.

When you evaluate a tool, map it against these seven stages explicitly. The gaps are where your team's manual work will continue to live, and vendors rarely volunteer them.

Manual review is entirely reasonable at low volume. It stops being reasonable at recognizable points:

• Applications accumulate in a shared inbox, and approval time is measured in days rather than minutes.
• Nobody can answer how many active trade accounts you have without building a spreadsheet first.
• Resale certificates live in a folder, and no one is confident which have expired.
• Reconstructing why a particular designer was approved requires finding the person who approved them.
• Approved applicants are re-keyed into the store by hand, with the tagging errors that implies.
• Your team is doing tax-compliance review as a side effect of doing customer service.

The last one is the expensive one. Reviewing exemption paperwork is specialized work being performed by people you hired to sell and to look after designers.

Feature lists converge; these are the axes on which tools genuinely differ.

The single most useful question to ask a vendor is which of their checks hit an authoritative external source and which are self-reported. A tool that asks an applicant to type their EIN and upload a business license has collected two documents. A tool that confirms the entity is registered and in good standing has verified something. Both may appear on a feature list as "business verification."

Checks worth insisting on

A serious verification stack draws on several independent signals, because any one of them can be stale or gamed:

• Business entity registration and EIN
• State sales tax registration
• Professional association membership
• An active business website, and how long it has existed
• Portfolio or social presence showing completed work
• Occupational licensure, in states that regulate the title
• A valid, current resale certificate
• Trade references from other brands
• Press coverage or showhouse participation

No single check is decisive. A newly formed studio run by an experienced designer will fail a longevity test; an established practice may not belong to any association. What matters is whether the tool surfaces the pattern clearly enough for you to make a fast decision, and whether it keeps the evidence.

Ask, too, about re-verification. A designer verified in 2024 whose sales tax registration lapsed in 2026 is a live exposure, and a one-time check at application will never catch it.

This is where the category divides most sharply, and where the language is least reliable.

Forty-six US jurisdictions impose sales tax—45 states plus the District of Columbia. Five states have no statewide sales tax at all. Most of the taxing jurisdictions publish their own exemption certificate form; two multistate instruments, the Multistate Tax Commission's Uniform Sales and Use Tax Exemption Certificate and the Streamlined Sales and Use Tax Agreement certificate, are accepted by some states and not others, with per-state conditions on their use.

Which certificate is valid for any given transaction depends on where the designer is registered, where you have nexus, and where the goods are going. That is a matrix, not a document.

The distinction to test

Ask the vendor to name the states they generate official pre-filled forms for, and the states where they only accept an upload. Then ask who is responsible when the wrong form is on file. A tool that stores documents is a filing cabinet with a search box—useful, but it has not moved the compliance burden off your team.

Test expiration handling as a scenario rather than a feature. Walk through the day a certificate lapses: who is notified, when, and does the tax exemption come off the customer record automatically or does it wait for someone to notice? In most states the vendor carries the assessment for tax-free sales made against an invalid certificate, so automatic revocation is a risk control, not a convenience.

An approval decision has no commercial value until it reaches the system that prices the order. Ask precisely what gets written, and treat a CSV export as a red flag rather than an integration.

On a well-integrated setup, approval should create or update the customer record, apply whatever tag or group your pricing rules key on, and set tax exemption per state rather than as one account-level switch—because a designer may be exempt in the states where they're registered and taxable elsewhere. If you run a B2B setup with company-level accounts, the same fields need to reach the company record, since that is what company-scoped price lists target.

Then ask the question most vendors haven't prepared for: what happens when someone on your team edits one of those fields by hand? Fields managed by an integration drift. A tool that detects and reports drift is telling you it takes ownership of the data; one that silently overwrites, or silently doesn't, is leaving you to discover the discrepancy during an audit.

Building the visible part is genuinely straightforward. An application form, a queue, an approve button, and a webhook into your store is a few weeks of work for a competent team, and if your trade program is a flat discount with no tax-exempt purchasing, that may be the correct answer. Build it.

The calculation changes entirely once exemption certificates are involved, because you are no longer building a workflow—you are committing to maintain tax content indefinitely. Form revisions, changing conditions on multistate certificates, and nexus thresholds that have been in motion since South Dakota v. Wayfair in 2018 all have to be tracked by someone, forever, and the cost of being wrong is an assessment rather than a bug report.

The bolt-on option—a tax engine alongside a form builder alongside your CRM—works, but be honest about where the seams fall. The seams are usually the verification decision and the provisioning step, which is to say the two places where a person ends up in the loop.

Bring these verbatim. Most are answerable in a sentence by a vendor whose product does the work, and produce a change of subject from one whose product doesn't.

1. Which of your checks hit an authoritative external source, and which are self-reported by the applicant?
2. Show me the evidence retained for a single approved applicant, as an auditor would see it.
3. Can my team change the auto-approval rules ourselves? Show me the screen.
4. Which states do you generate official forms for, and which do you only accept uploads for?
5. How do you decide which certificate form is valid for a given designer, my nexus, and the ship-to state?
6. What exactly gets written to my commerce platform on approval—fields, tags, tax settings?
7. Is tax exemption applied per state, or as a single account-level flag?
8. What happens if someone on my team edits one of those fields by hand?
9. Walk me through the day a certificate expires. What happens automatically?
10. Link an order to the certificate that justifies its exemption, in front of me.
11. How do you price, and what specifically moves us to the next tier?
12. Do you take any percentage of sales, transactions, or designer spend?

Ask for the fifth and tenth as live demonstrations rather than descriptions. Reconstructing an audit trail in front of a prospect is easy if the data model supports it and impossible if it doesn't.

This is the part of the guide where we describe our own product, so read it accordingly.

Credenza is trade program software for interior design vendors, built around the three stages that are hardest to do by hand. Verification runs up to nine evidence checks against authoritative sources and surfaces the result as a decision, not a document pile. Certificate generation produces compliant certificates across the 46 taxing jurisdictions, auto-filling 39 official state forms, matched to your nexus and the destination state. Onboarding applies your auto-approval rules and writes the approved designer into your commerce platform with state-scoped tax exemption applied, then monitors certificates for expiry, chases renewals, and revokes exemption if a certificate lapses.

Credenza is not a commerce platform and does not replace one—it complements B2B setups by handling identity, verification, and compliance, which those platforms leave to you. It is not a marketplace: designers apply to the brands they choose, and your trade relationships remain yours.

Where we'd tell you to look elsewhere: if your trade program has no tax-exempt component, most of what Credenza does is overhead you don't need.