We've seen wholesale and distribution businesses kept circling back to one mess: the catalog lived in a spreadsheet, prices lived in four more spreadsheets, and "can you send me the latest file?" was a daily message in someone's inbox.

The spreadsheet is not the failure. The failure is stacked versions of the truth: each customer pays a different price, stock moves hourly, and the file you exported this morning is wrong by lunchtime.

We kept building the same fix as custom work, so this time we built it once: SkuHQ.

How it works:

You import your catalog from Excel or CSV. You manage SKUs, attributes, measurements, images and brands in one portal.

Then you connect customers: each one gets their own pricelist and their own API key, and every request resolves prices through that customer’s pricelist. Same SKU, different price, no manual copies.

The part we care most about: not every reseller has a developer. For them, SkuHQ generates a private live catalog link. It opens in their browser, shows only their prices and their product range, includes live stock, and can be revoked in one click from the portal. No login, no install, no emailed PDF.

SkuFeed is included free on every plan: a small desktop app you point at a folder of exports. It keeps prices and stock synced.

What SkuHQ does not do: orders, quotes, invoicing, shipping or B2C storefronts. It handles catalog, pricing and stock, and plugs into whatever handles the rest. Ordering is planned for V2.

And we are a small team: support is email, priority on the higher plans.

The thing we keep debating: what share of resellers would realistically use an API key instead of the live catalog link? If you distribute products, we would genuinely like to know how you expect that to split, and what would need to exist in the API before you would switch your own feed over.