How to Create a Digital Catalog for Field Sales Teams

Your reps are still carrying a three-ring binder. The prices in it were right in March. Two of the SKUs were discontinued, one has new packaging, and the "special" on page 14 ended before the last trade show. Every order that comes back from the field needs a phone call to confirm what the customer actually meant.

That is the real reason companies start asking how to create a digital catalog. It is not about looking modern. It is about killing the gap between what you sell and what your team can show, quote and order on the spot.

This guide covers the practical build: the data you need, the images, the pricing rules, the offline problem, and how to launch without your sales team quietly going back to the binder.

What a Digital Catalog Actually Has to Do

Before you pick a tool, get specific about the job. A digital catalog that tries to be everything to everyone ends up as a PDF on a shared drive — which is a binder with extra steps.

In practice, a catalog that earns its keep does three things.

It answers the buyer's question in under ten seconds

Your customer wants to know: do you have it, what does it cost me, when can I get it. Everything else — the spec sheet, the lifestyle photo, the brand story — is supporting material. If those three answers take more than a couple of taps, reps will memorize prices instead, and memorized prices are wrong prices.

It turns browsing into an order

The moment a rep has to switch from the catalog to a paper order form, you have lost the data. Build the cart into the catalog. Line items, quantities, customer-specific pricing, notes, signature — all in the same flow. This is the difference between a catalog and a sales rep app with a digital catalog that actually closes the loop into your ERP.

It stays correct without anyone remembering to update it

If keeping the catalog current is somebody's weekly chore, it will be out of date within a quarter. The catalog should read from the same system of record as your inventory and pricing, not from a spreadsheet someone exports on Fridays.

How to Create a Digital Catalog in Seven Steps

Here is the sequence that tends to work for distributors, manufacturers and wholesalers with somewhere between a few hundred and a few hundred thousand SKUs.

1. Pick the audience first. A catalog for your own field reps, a self-service portal for existing accounts, and a public catalog for lead generation are three different products with three different data requirements. Build one. Add the others later.
2. Audit your product data. Export everything you have. Count how many SKUs are missing a description, a price, a unit of measure or an image. That number is your project timeline.
3. Define the required fields and refuse to launch a SKU that is missing them.
4. Standardize images against a naming convention tied to the SKU.
5. Set the pricing rules — list price, customer tier, volume breaks, promotions, and who is allowed to override.
6. Decide how it behaves offline, because basements and loading docks do not have signal.
7. Pilot with three reps for thirty days before you roll out to everyone.

Notice that six of the seven steps are about data and rules. The screen design is the easy part.

Product Data: the Part That Sinks These Projects

Nearly every stalled digital catalog project we see is a data project wearing a design costume. The build looks fine in the demo with twenty hand-picked products, then collapses when the real 14,000-SKU file lands.

The minimum viable field list

For each sellable item, treat these as non-negotiable:

• SKU or item number — exactly as it appears in your ERP, no cosmetic variations
• GTIN or UPC where one exists, so barcode scanning works in the aisle
• Short name (under 60 characters) and a longer description
• Unit of measure and pack hierarchy — each, inner, case, pallet, with the conversion factors
• Category and subcategory, using one taxonomy, not three inherited ones
• Price basis and the unit that price applies to
• Status — active, discontinued, special order, seasonal
• At least one image

Pack hierarchy is where ordering errors come from. A rep taps "12" meaning twelve cases; the system reads twelve eaches. Make the unit explicit on screen, every time, in words. If you use GTINs, GS1 US publishes the standards for how those identifiers are structured and assigned — worth following rather than inventing your own scheme.

Images: boring rules beat good taste

Set the standard once and apply it to everything: same aspect ratio, same background, same minimum resolution, filename built from the SKU. Something like SKU12345_01.jpg, SKU12345_02.jpg.

Two reasons this matters more than it sounds. First, a catalog where some products have crisp white-background shots and others have a phone photo taken on a shop floor reads as careless, and buyers transfer that judgment to your fulfillment. Second, SKU-based filenames let you bulk-load thousands of images without a human matching them one at a time.

Compress aggressively. Serve a thumbnail in the grid and the full image only when someone taps it. A rep in a parking lot on a weak connection will abandon a catalog that takes eight seconds to paint a product list.

Who owns the data

Name one person. Not a committee, not "marketing and operations together." That person approves new SKUs into the catalog and has the authority to hold back an item that arrives without a description or an image. Without this role, standards decay quietly over about two quarters.

Pricing, Availability and the Offline Problem

These three decisions determine whether your sales team trusts the catalog.

Pricing. Decide whether the catalog shows list price, the logged-in customer's price, or both. B2B buyers generally want their price. That means your catalog needs the customer context at login and a pricing engine that resolves tier, contract and promotion in the right order. Write that order down explicitly — ambiguous precedence rules produce quotes you have to honor and did not intend.

Availability. Real-time stock numbers are the honest answer but they create a support burden when the number is wrong. A middle path many distributors use: show status bands instead of counts — in stock, low, lead time of roughly two weeks, special order. You keep the useful signal without implying a precision your warehouse data cannot back up.

Offline. Assume no connection. Cache the catalog, the customer's pricing and the open order on the device, queue submissions, and sync when signal returns. Then handle the conflict case: what happens when a rep writes an order offline for an item that sold out an hour earlier. The usual answer is to accept the order, flag the line, and notify customer service — not to silently drop it.

One more practical note. If your catalog is also customer-facing, it is now part of your revenue infrastructure, which means uptime is a sales problem rather than an IT problem. Decide what your tolerance for downtime is before you find out the hard way.

Launch Checklist and What to Measure

Run through this before the catalog goes to the whole team:

• Every live SKU has the required fields populated
• Every live SKU has at least one image at your standard
• Discontinued items are hidden or clearly marked, not just left in place
• Search returns sensible results for misspellings and partial item numbers
• Three reps have placed real orders through it end to end
• Orders land in the ERP without manual re-entry
• The catalog loads and takes an order with the device in airplane mode
• One named person owns new-SKU approval

Then track four numbers for the first ninety days: share of orders submitted through the catalog, average lines per order, time from order to confirmation, and order error rate. If the first number stalls below half, your reps are telling you something — usually that search is bad, pricing is wrong, or the item they sell most is missing.

E-commerce is a growing share of US sales across channels; the U.S. Census Bureau publishes the quarterly figures if you want a baseline for how your own digital order share compares to the broader trend.

Build, Buy or Something in Between

If your products are simple, your pricing is simple, and you sell standard units, an off-the-shelf catalog or B2B commerce platform will get you there faster and cheaper. Use it.

Custom becomes the right call when the complexity lives in your rules: pack hierarchies that vary by customer, contract pricing with unusual precedence, route-based availability, direct store delivery where the catalog and the truck inventory have to agree. Those are the cases where configuring a generic platform costs more than building the thing you actually need.

A note on capacity, since this is usually the constraint rather than the budget: our team in Mexico works US business hours, which means the data cleanup and the daily back-and-forth on edge cases happen in the same workday as your operations team rather than overnight. For a project that is 70% data decisions, that overlap matters more than it does on a pure build.

Start with the audit. Export your product file this week and count the gaps. Once you know how many SKUs are missing a price, a unit or an image, you will know whether you are three weeks from a working digital catalog or three months — and either answer is better than guessing.

If you want a second opinion on the approach before you commit engineering time, get a quote for your project and we will walk through your product data with you.