Product Catalog Management Services

Collect authoritative product inputs

Provide SKU lists, category rules, approved descriptions, image references and price sources. Define units, required attributes and the relationship between parent products and variants before copying data between sales channels.

Check relationships and publication

Verify unique sellable identifiers, variant combinations and image association. Hold missing prices, contradictory specifications or unsupported product claims for approval. Test a limited import and inspect the visible product page before releasing a batch.

Estimate by catalog structure

Assess variation count, attribute depth, source quality, localization and channel differences. Agree whether charging follows products, variants, channel listings or accepted changes, including the treatment of repeated revisions to commercial inputs.

Model the sellable unit before making a channel file

A parent product groups options; a variant identifies a sellable combination; a channel listing represents that combination under a marketplace or storefront schema. Keep their identifiers separate. A parent title can be shared, while price, barcode, stock unit and image may belong to a variant. Copying a parent image into every row can produce a technically accepted file with misleading customer choices.

Create a channel mapping for required attributes, category values, image constraints and publication states. Mark the authoritative source for each commercial field and who approves a change. An operator can map an approved material description but should not infer a safety claim or invent a missing barcode to satisfy a channel validator.

Illustrative example: one shirt, four variants, two channels

In this hypothetical catalog, parent SH20 has blue and white shirts in sizes S and M. The client supplies four SKU records, approved prices and image filenames. Channel A accepts a parent with four variant rows; Channel B needs four separate listing IDs. The operator maps the same SKU to both schemas and checks each selected color against its image. White/M lacks an approved image and is held on both channels.

The client’s merchandising owner approves publishing the other three variants. Channel A accepts all three; Channel B accepts two and rejects SH20-BM because its size value must be “Medium,” not “M.” The operator corrects the channel mapping, retries only that rejected listing, and retains the receipt. Acceptance is six successful channel listings for three SKUs plus two held listings for White/M, not eight published listings.

Check the visible product after a successful import

Import receipts show whether the platform processed a row, not whether customers see the intended choice. For an agreed test set, select each option on the storefront and verify displayed SKU, image, price, unit and availability against the approved input. Include a product with multiple option dimensions because flat single-SKU items do not test variant relationships.

Capture the destination listing ID and check time so later price or inventory changes are not confused with an import defect. Publication approval should specify whether a hidden draft, a scheduled item or a live listing is the accepted state. Administrative preparation does not itself authorize a public commercial promise.

Count rejections and revisions at the right level

Track parent count, variant count and channel-listing count separately. Four SKUs on two channels can require eight destination outcomes. A failed row may need a mapping correction, a new source value or channel-owner intervention; these are different causes with different correction responsibilities.

Store batch versions and retry only the affected identifiers. Agree how the buyer will approve changed prices, replaced images and deleted variants after the initial delivery. A reusable mapping and exception register are more valuable than a one-off import that cannot explain which source created each public field.