How to Compare 3PL SKU Setup and Master-Data Fees

Compare 3PL SKU setup fees by separating the initial item record from ongoing master-data changes, physical measurement, barcode validation and workflow configuration. A low per-SKU fee may cover only a basic name and barcode. Another provider may include dimensions, weights, pack hierarchy, lot or expiry rules, dangerous-goods fields and channel mappings. Those offers are not equivalent.

Good master data supports receiving, storage, picking, packing, rate shopping and channel compliance. 247 Fulfillment’s integration overview describes ecommerce, marketplace, ERP, API and EDI connections. Those connections move data, but the underlying product record still needs clear ownership and validation.

Define the minimum item record

Start with the fields required for every SKU, then add conditional fields by product type and channel. Do not ask providers for “SKU setup” pricing until the record is defined.

Ask which fields the brand supplies and which the warehouse measures or validates. If the 3PL captures dimensions, specify equipment, precision and whether the record stores product-only or packaged-shipping dimensions. Those values serve different decisions.

Separate one-time setup from recurring change work

The commercial schedule should identify at least four events:

• Initial import: creating records from a clean template or integration.
• Physical validation: measuring, weighing, scanning or photographing inventory.
• Complex configuration: lot, expiry, serial, dangerous-goods, kitting or channel-specific rules.
• Ongoing change: updating barcodes, descriptions, pack quantities, dimensions, statuses or mappings after launch.

A fifth event is correction of rejected or incomplete data. Ask whether the provider returns an error file for the brand to fix, charges for manual cleanup, or both. Define when a record is accepted and when inventory can be received against it.

Changes should be controlled after launch. An unreviewed pack-quantity change can create inventory errors; a dimension change can affect packaging or carrier rating; a barcode replacement can interrupt scanning. Record who requested, approved and implemented each change and when it became effective.

Ask what the fee actually includes

A per-SKU setup fee may include a standard template review, record creation and barcode test. It may exclude physical handling, photography, channel mapping, custom fields, integration work and later changes. Ask providers to mark every item as included, priced separately or unavailable.

For imported records, confirm whether the provider charges per submitted row or per successfully activated SKU. Duplicate, inactive and child-variant records can inflate a row-based charge. For ongoing changes, ask whether fees are per field, per SKU, per request or hourly, and whether a minimum applies.

Worked example: model year-one master-data cost

Hypothetical example in Canadian dollars; these are not 247 Fulfillment rates. A brand launches 250 standard SKUs. Each month it expects 40 simple record updates and six complex changes that require physical handling or workflow review.

The average year-one cost is CAD $3,990 ÷ 250 = CAD $15.96 per launch SKU, but that ratio includes recurring work across the whole catalogue. The initial CAD $3.00 rate is only 18.8% of the modelled total. In this scenario, change frequency and complexity matter more than the onboarding headline.

The recommendation changes if the catalogue is stable, if the ERP remains the authoritative system and updates flow automatically, or if most SKUs require lot, serial or compliance rules. Model the volume of each change type rather than applying one average to all records.

Test the control path before launch

Use sample SKUs that represent normal, complex and exception cases. Confirm how the system rejects a duplicate barcode, a missing weight, an invalid case quantity or an unsupported value. Then change one critical field and inspect the audit trail.

Define system ownership. If the ERP is authoritative, decide whether warehouse edits are prohibited or written back. If the 3PL measures a product and finds a conflict, state whether it may update the record, open an exception or wait for brand approval. 247 Fulfillment’s inventory management overview can help frame the fields and statuses that matter in operation.

Buyer checklist

• List mandatory and conditional fields by product type.
• Define the authoritative system for each field.
• Separate import, validation, configuration and recurring-change fees.
• Confirm billing treatment for rejected, duplicate and inactive records.
• Price physical measurement, photography and barcode work separately.
• Require approval and an audit trail for critical changes.
• Test standard, complex and failed records before launch.
• Model year-one cost using real catalogue-change volume.

Include your SKU count, item template, product attributes, source systems and expected monthly change volume in the quote request. That lets the provider scope data work instead of guessing from the catalogue size alone. Use 247 Fulfillment’s contact form to share those assumptions.