Marketplace requirements change, and they differ between platforms and between countries within the same platform. Nothing below should be treated as the current rule for any specific marketplace — always confirm the live requirements in your seller account for your destination before locking a specification. What does not change is the structure of the problem: online channels impose unit-level identification, item-level protection, and prep standards that traditional wholesale packaging was never designed to satisfy.

This guide sets out those categories so buyers can brief a factory properly and decide what to have done at source rather than paid for later at a fulfilment centre.

1. Why Marketplace Packaging Is a Different Specification

Wholesale packaging assumes a carton is opened by a retailer who merchandises the contents. Marketplace fulfilment assumes each unit is an independently stored, picked, and shipped object. That single difference generates most of the requirements: every unit needs to be scannable on its own, sealed so contents cannot separate, and robust enough to travel alone rather than cushioned by a full carton.

It also changes who pays for mistakes. A retail buyer who receives mislabelled goods sends a complaint; a fulfilment centre applies a fee per unit, or refuses the shipment. Because these fees are charged per unit, a labelling decision that seems minor at order stage scales into a real number across a few thousand pieces.

2. Barcodes and Unit-Level Identification

Every sellable unit needs a scannable barcode, and buyers should be clear which type their channel requires. Typically this means a retail product code (UPC or EAN) obtained by the seller, and in some fulfilment models a marketplace-specific unit label generated in the seller account and applied to each item. The two are not interchangeable, and some programs require the marketplace label to cover or replace the manufacturer barcode entirely.

Practical points to settle before production:

  • Which code type each SKU carries, and who generates it — codes are the seller's responsibility, not the factory's
  • Whether the factory applies the label at source or the seller's prep service applies it later, and the per-unit cost of each route
  • Where the label sits — a flat, scannable surface, not wrapped over a curved edge or a seam
  • Label material and adhesive, so it neither peels in transit nor tears the packaging when removed
  • Whether variations (colour, size) each need their own distinct code, which for an eyewear assortment they normally do

Send the factory the actual label files with a clearly marked placement diagram, and ask for a photograph of a labelled unit before bulk labelling begins. A scan test on a sample costs nothing and catches placement problems that are otherwise found by a fulfilment centre.

3. Polybags, Seals, and Required Warnings

Many fulfilment programs require sealed unit packaging, and where a transparent polybag is used, warning text about suffocation risk is commonly required above a certain bag size, in a specified minimum text size. For children's products this area deserves particular care, and the exact wording and thresholds should be taken from the marketplace's current published requirements rather than copied from another seller's listing.

For eyewear specifically, buyers should also decide whether the polybag is the presentation or merely a protective layer over a printed box or pouch. If the bag is what the customer opens, it becomes part of the unboxing experience and its print quality and seal neatness matter commercially, not just operationally.

4. Surviving the Parcel Journey

A pallet journey protects goods collectively; a parcel journey does not. Individual units are conveyed, chuted, sorted, and sometimes shipped in their own packaging without an outer box. Eyewear is light and rigid — it does not crush like soft goods, but hinges, applied charms, and lenses are all vulnerable to point impacts.

Sensible specification points include a rigid or semi-rigid inner (a case, a moulded tray, or a box with an insert that stops the frame moving), enough internal restraint that the item cannot rattle, and consideration of whether the pack can ship without additional overboxing. Where a marketplace offers a ship-in-own-container option, packaging that qualifies avoids both the extra box and the fee — but it usually has to pass a drop and handling test, so ask the supplier what protective construction they can offer and validate with a real sample rather than assuming.

5. Case Packs, Cartons, and Prep at Source

Even in online channels, goods still arrive at the warehouse in cartons — and the carton specification has its own rules. Buyers should confirm units per carton, whether cartons are single-SKU or mixed, maximum carton weight and dimensions accepted by the destination facility, and what carton-level labelling is required in addition to unit labels.

Mixed-SKU cartons are worth a decision rather than a default: they suit small assortments but often trigger additional handling requirements at the fulfilment centre. Single-SKU cartons process faster and are usually preferred once volume per SKU supports them. The related choice is where prep happens — at the factory, or at a third-party prep service near the destination. Doing it at source is almost always cheaper per unit, but only works when the specification is exactly right, because correcting a labelling error after arrival costs far more than the labels did.

6. Getting the Factory to Ship Channel-Ready

Factories can usually meet marketplace prep requirements, but only if they are given the requirements rather than asked to infer them. A workable brief includes:

  • The label files themselves, per SKU, with a placement diagram and required orientation
  • Whether each unit is polybagged, and the bag specification including any required warning text
  • The inner protection format and how the frame is restrained
  • Units per inner pack and per carton, and whether cartons are single or mixed SKU
  • Carton weight and dimension limits for the destination facility
  • A named sample unit to be photographed and approved before bulk packing

Buyers should also expect these items to carry their own minimums and lead times, exactly as retail packaging does, and to appear as separate lines on the quotation rather than being absorbed into the unit price.

7. Confirm Before Production, Not After Arrival

The failures in this area are cheap to prevent and expensive to fix, because they are discovered at a facility that charges per unit to correct them. Before production starts, a seller should have: current requirements pulled from their own seller account for the destination country, label files issued per SKU, an approved photograph of a fully packed and labelled sample unit, a successful scan test on that sample, and a written carton specification the factory has confirmed.

One habit is worth building for anyone running these channels long-term: re-check the marketplace's requirements before each production run rather than reusing last year's specification. These rules are revised periodically, and a specification that was compliant on the previous order is not automatically compliant on the next one.

Summary: Online channels need unit-level identification, sealed and protected individual units, and carton specifications the destination facility accepts — none of which retail packaging provides by default. Settle code types and label placement with the factory using real label files, decide polybag and warning requirements from the marketplace's own current documentation, specify inner protection for a parcel rather than pallet journey, and choose deliberately between single and mixed SKU cartons. Approve a photographed, scan-tested sample unit before bulk packing, and re-check requirements each run rather than reusing an old specification.

Selling kids eyewear through online channels?

Share your marketplace prep requirements, label files, and carton limits so packaging, labelling, and protection can be specified before production rather than corrected at destination.

Back to Insights