← SKU Monster · Blog
July 4, 2026 · SKU Monster

You just bought a pallet. The manifest is a spreadsheet with a few hundred barcodes, maybe a rough description column, and prices that were relevant to somebody else's business. Before any of that inventory earns a dollar, every SKU needs a compliant main image, a handful of supporting shots, a title, a category, and specs — and doing that by hand across a full manifest is the slowest, most expensive part of reselling liquidation stock.

This guide shows a repeatable pipeline for turning that manifest into a listing-ready catalog: barcodes in, compliant images and structured data out.

What You'll Learn

Step 1: Clean the manifest down to its barcodes

A liquidation manifest is rarely clean. You'll see merged cells, inconsistent condition codes, and free-text descriptions that vary from "blender" to a full model string. The one column that matters most for automation is the barcode: the EAN, UPC, or other GTIN.

Extract that column into a simple list. Strip spaces, drop non-numeric junk, and remove obvious duplicates. Keep the original row index so you can map results back to quantities and lot pricing later. At this stage you don't need images or descriptions to be good — you just need clean identifiers, because a barcode is the key that unlocks everything downstream.

If your manifest has no barcodes at all, only descriptions, this pipeline won't help directly; you'd need to source GTINs first. Most liquidation and wholesale manifests do include them.

Step 2: Look up one SKU to validate the data before you spend

Before processing hundreds of rows, test the pipeline on a single barcode. SKU Monster has a free lookup on the home page that needs no account, so you can confirm the flow with your own inventory in seconds. Try it at sku.monster.

Under the hood, a single lookup hits the barcode endpoint:

GET /api/v1/barcode?code=0000000000000
x-api-key: <your-key>

That returns structured product data — name, brand, category, specs, and images — for the identifier. The response shape is straightforward: a product object with fields and an image set. (That's an illustrative description of the shape, not a copied response; run it against your own SKUs to see the real fields.) The full field reference lives in the API docs.

The point of this step is trust. You are a technical buyer; test the claim on a barcode you can physically verify against the box in front of you, then scale.

Step 3: Understand what marketplace images actually demand

Here is why raw manifest photos — usually a warehouse phone snapshot, if you get anything at all — don't cut it. Marketplace image rules are strict and enforced by automated checks that often give you no useful error message when you fail.

A few concrete requirements you're building toward:

When images fail these checks, the failure is quiet. Sellers face listing suppression or downranking with no useful error message, which is exactly why liquidation catalogs stall out — you don't always know a listing is buried until it never sells. Non-compliant images have been documented to delay approval for new ASOS partners and suppress visibility on Zalando via its Product Content Score, causing real revenue delays.

The fix isn't only the main image. Amazon allows up to 15 additional images plus a thumbnail, Walmart recommends a minimum of four images per listing, and eBay data shows listings with high-quality extra images are 20% more likely to sell fast and about 4% more likely to convert per added picture. More accurate, multi-angle imagery reduces buyer doubt and directly affects how fast your liquidation inventory clears.

Step 4: Generate compliant images and data per SKU

Instead of hunting down or shooting photos yourself, SKU Monster takes a barcode and automatically finds and generates clean, white-background, studio-quality product images plus structured product data. To be precise about what that is: it's an automated image and data pipeline, not a licensed archive of pre-shot photography. It builds the assets for the identifier you give it.

For a single identifier you can trigger image generation:

POST /api/v1/images
x-api-key: <your-key>
Content-Type: application/json

{ "identifier": "0000000000000" }

The output is designed around what marketplaces demand — white backgrounds and studio framing — so you're not manually re-editing every shot to pass a content-score check. SKU Monster produces five studio-quality images per SKU, which lines up well with Walmart's four-image minimum and gives you supporting angles beyond the required main shot.

At $2 per SKU with no subscription, the cost math against a liquidation pallet is simple: traditional product photography runs roughly $250–$1,500 per SKU, and manual data entry adds hours per listing. For inventory you bought cheaply and need to move quickly, per-SKU automation is what makes the economics work. See current per-SKU pricing on the pricing page.

Step 5: Batch the whole manifest

Once the single-SKU flow is validated, run the full manifest in one job rather than looping requests one at a time. The batch endpoint is built for exactly this:

POST /api/v1/batch
x-api-key: <your-key>
Content-Type: application/json

{ "codes": ["0000000000000", "0000000000001"] }

Feed it the cleaned barcode list from Step 1. Because you preserved the original row index, you can map each result back to its quantity, condition, and lot cost from the manifest — producing a catalog that's ready to import into Shopify, Amazon, eBay, WooCommerce, or Walmart.

Expect some SKUs to come back without a confident match. A liquidation manifest will always contain private-label goods, regional variants, discontinued items, or plain bad barcodes. Don't treat unresolved rows as a failure of the pipeline — treat them as a triage queue. Set the resolved SKUs live first so revenue starts flowing, then handle the exceptions manually or drop the ones that aren't worth the effort. The whole point is to spend your manual time only on the rows that actually need it, instead of on every single line.

For rate limits and error handling when you batch at scale, check /docs/rate-limits and /docs/errors so a large job doesn't stall on retries.

Summary

Turning a liquidation manifest into a listing-ready catalog comes down to one insight: the barcode is the key. Clean your manifest to its GTINs, validate a single lookup for free, understand the real marketplace image rules — 1,600px minimum, pure white backgrounds, 85–90% framing — and then batch the whole list so a barcode becomes five compliant studio images plus structured data. The SKUs that resolve go live fast; the ones that don't become a short manual queue instead of a mountain. That's how you turn a pallet's manifest into a catalog that actually sells.

Ready to Try It?

Test a barcode from your own manifest with the free lookup, then create an account to batch the whole pallet. Get started at sku.monster/register.

← More posts