There is a peculiar contradiction sitting at the heart of wholesale commerce that almost nobody talks about openly, even though every retailer has lived it so many times that it barely registers as remarkable anymore.

A brand spends years and considerable resources building a product line — obsessing over materials, finishes, and packaging, commissioning lifestyle photography with professional food stylists, hiring creative agencies to craft a visual identity. They will send you a folder of 400 carefully art-directed JPEG files, each named something like IMG_8847_FINAL_v3_USE_THIS_ONE.jpg, without anyone asking. The images arrive the same day. Then you ask for a product file — the SKUs, barcodes, titles, and dimensions that allow you to actually put those products in front of customers — and something fundamental breaks down in the relationship.

The File That Never Comes

Every retailer who has onboarded a new vendor knows exactly how this goes. You make a reasonable request for structured product data: SKUs, UPCs, titles, descriptions, weights, dimensions. The kind of information that clearly exists somewhere inside that organization, because they manufacture the products, ship them in boxes with labels, invoice them, and manage them in whatever system keeps their warehouse running. The data is there. What arrives instead tends to be one of a predictable set of non-answers — a PDF lookbook, a Google Drive link to the same images they already sent, a promise that a proper file is “being finalized” that somehow never quite reaches you, or eventually, a spreadsheet with column headers buried in row four, merged cells that refuse to parse, and a SKU column that Excel has helpfully formatted as currency.

The remaining five percent or so — the brands who send a clean, complete, ready-to-upload file with consistent SKUs, valid UPCs, useful descriptions, dimensions in the right units, and images named after the products they depict — get talked about. Buyers remember them. Reorder rates from those vendors tend to be higher, not just because the products sell but because working with them doesn’t require a data recovery operation before a single item can go live.

A Contradiction Worth Naming

What makes this genuinely strange is that the entire value proposition of a wholesale network is that other people sell your products for you. The brand makes, the retailer sells, and the arrangement benefits both sides. But when you ask a brand to support the selling side of that equation — to provide the basic digital infrastructure that modern commerce requires — a surprisingly large number of them respond as though you’ve asked for something unusual or burdensome, rather than something that is entirely in their own interest to provide.

They want resellers to sell their products. They just haven’t paused to consider, even for a moment, what that actually requires in practice.

A product does not sell online simply because it exists in a catalog. It sells because a customer can find it through search, understand what it is from the title and description, trust it enough to add it to a cart, and complete the transaction without confusion. That chain of events requires a title that actually describes the product, a description that explains its value, a barcode that scans at the point of sale and reconciles correctly with the order, dimensions and weight so that shipping can be calculated accurately, and images that are organized and labeled in a way that allows a human being to match them to the right product without becoming a detective. All of this information exists within the brand already. It simply hasn’t occurred to most of them that their resellers need it too.

The Realistic Best Case

In practice, the most a retailer can reasonably hope to receive from the majority of vendors is a spreadsheet containing three columns: SKU, UPC, and title. That modest baseline, which most brands could produce in an afternoon from whatever system they already use, represents the ceiling of what many wholesale operations will deliver. Descriptions, dimensions, weights, and properly organized images are things the retailer will typically build from scratch — by scraping the brand’s own website, cross-referencing a PDF lookbook, or in some cases photographing products in their own back office because the “high-resolution images” provided are 800 pixels wide and watermarked.

The practical implication: the retailer ends up doing the brand’s content work for them, absorbing that cost invisibly, while the brand continues to wonder why certain resellers perform better than others.

What Good Actually Looks Like

The brands worth studying are the ones who have figured out that product data is a distribution asset, not an administrative afterthought. They maintain a partner portal — a self-serve area where any authorized reseller can log in, select the products they carry, and download a properly formatted file for whichever platform or system they use. Not one universal export that nobody’s system quite accepts, but actual platform-specific files built to the import specifications of the tools their retailers actually run.

That kind of infrastructure, built once and maintained as the catalog evolves, would support the full range of platforms that retailers operate on today:

eCommerce

• Shopify
• WooCommerce
• BigCommerce
• Magento / Adobe Commerce
• Salesforce Commerce Cloud
• Squarespace Commerce

ERP & Inventory

• NetSuite
• SAP
• Microsoft Dynamics 365
• Epicor
• QuickBooks Commerce
• Sage 100 / 300

Point of Sale

• Shopify POS
• Lightspeed Retail
• Square for Retail
• Clover
• Revel Systems
• Toast

Marketplaces

• Amazon Seller Central
• Google Shopping
• Meta Commerce
• TikTok Shop

A reseller using Lightspeed at their physical locations and Shopify for their online store needs two different files with different column structures, different required fields, and different image naming conventions. A brand that can deliver both — accurately, on demand, without requiring a phone call — has just removed a significant barrier to their own products being well-represented wherever they’re sold.

The Cost of Inaction

The math here isn’t complicated. Every hour a retailer spends building product data that the brand should have provided is an hour not spent on marketing, merchandising, or customer service. That cost is invisible to the brand (it doesn’t appear on an invoice) but it shapes everything from how prominently the product is featured to whether the retailer bothers to add new SKUs when they’re announced. Brands with strong data programs end up better positioned on the shelves and better described on the product pages, not because their retailers like them more, but because working with them doesn’t require a data recovery operation before a single item can go live.

Building a proper product data feed is not a complex undertaking. The data exists. The platforms that can format and distribute it exist. What’s missing, in most cases, is the recognition that product data is part of what a brand owes its retail partners — as fundamental to the wholesale relationship as terms, minimums, and lead times. Until that recognition becomes standard, retailers will keep building the catalog themselves, one product at a time, from whatever sources they can find.

The images will always be there, of course. There are always plenty of those.

Foxco builds and manages eCommerce operations for brands, manufacturers and retailers. If your catalog needs work, trust us — we’ve seen worse.