Skip to content
DashForDevs
A distributor and a trade buyer talking beside stacked pallets in a bright warehouse.

Wholesale And Retail On One Catalog.

A distributor running a trade portal beside a consumer store usually runs two systems and reconciles them. Here they are two front ends on one backend: one catalog, one order list, one customer record, different pricing and different rules.

What A Trade Operation Needs

The rules, mostly. The catalog is the easy half.

Architecture

Two Fronts, One Catalog

A wholesale portal and a retail store with separate domains and separate keys, sharing one catalog and one order list. Adding a product once means adding it once.

Pricing

Volume Tiers

Discount tiers keyed to order size, so a buyer taking a pallet is priced differently from one taking a case without anybody maintaining a second catalog.

Compliance

Restricted By State

Products can be locked to the states they may ship to, enforced in the cart. For regulated categories that is frequently the reason a distributor is shopping for new software at all.

Sales

Orders Placed For Buyers

Draft orders, because a good share of wholesale still happens on the phone. A rep builds it against real pricing and the buyer receives it.

Accounts

Buyers Who Sign In

Real accounts with verified emails, their own order history and tags, so which buyer sits in which programme is a property of the record.

Back Office

One Place To Work

Trade and retail orders share statuses and screens, so nobody runs two dashboards and reconciles them weekly.

The Gap You Should Know About.

There are no per-account price lists. If your business runs on a negotiated price for each buyer, this platform does not do that today: customer-specific product pricing is deferred work rather than a feature.

That is the first thing most distributors ask, so it belongs on the page rather than on a demo.

What Exists Instead.

Volume pricing keyed to order size, and separate pricing on the wholesale storefront. Between them they cover a large share of distributors, particularly those whose pricing is really tiered by quantity rather than negotiated per account.

Whether they cover yours is a five minute conversation and worth having before anything else.

It Reads From The Same Records

Build

The Portal Itself

Storefronts

Two Front Ends

Orders

Draft Orders

Questions People Ask

Can we price per customer?

Not per individual account, and that is the honest limit today. What exists is volume pricing keyed to order size and separate pricing on the wholesale storefront. If negotiated per-buyer price lists are how your business runs, treat that as deferred work rather than a feature you will find.

Can wholesale and retail share a catalog?

That is the normal setup rather than an upgrade: two storefronts, two domains, two API keys, one catalog and one order list underneath.

Can we restrict products by state?

Yes, at product level, enforced in the cart rather than described in a policy. In regulated categories this is often the deciding requirement.

What about buyers who order by phone?

Draft orders exist for exactly that. A rep assembles the order against the live catalog and pricing and sends it on, so the record stays in the system instead of in an inbox.

Do buyers need approving before they can order?

Most trade operations gate access at the account level rather than letting anyone with an email buy at trade pricing. How that gate works for you is part of scoping, because the answer differs between fifty accounts and five thousand.

Describe How Your Buyers Buy.

Volumes, terms, who sees what, and how much still happens on the phone.