Skip to content

SKU-Level Pack Instructions and Packaging Specifications

By Noah Loul · Reviewed by Noah Loul · Updated

  1. 01Your data spec
  2. 02Matched to businesses
  3. 03Rights and samples reviewed
  4. 04Licensed delivery
How it works with SourceX: Your data spec → Matched to businesses → Rights and samples reviewed → Licensed delivery.Illustrative

Short answer

SKU-level pack instructions are structured text that states how each item should be packed: carton choice, orientation, void fill, inserts, labels and handling marks. They can give a humanoid program task rules, success criteria and language for packing demonstrations, but they contain no motion, force or perception data and usually belong to brands or their 3PL clients.

The buyer's problem

Packing video shows what a worker did, not what the worker was supposed to do. When a packer places a glass jar upright, adds two paper fills and seals with a fragile label, the clip alone cannot tell a model whether that was a rule, a habit or an error. Pack instructions supply the intended rule for each item, which lets you check the video against it, label steps, and write evaluation criteria.

This page covers where such documents live, what fields to expect, and how to judge them. For the demonstration side, see packing demonstrations. For the general limits of written procedures, see what SOPs can and cannot teach a humanoid.

Where documented packing rules exist

  • Brands and shippers hold packaging specifications for their products: approved cartons, test requirements, retail-ready formats.
  • 3PL and fulfillment operators keep per-client, often per-SKU, pack-out instructions inside the warehouse management system or in client onboarding documents. These reflect client preferences such as branded tissue, inserts or gift options.
  • Contract packagers and co-packers hold work instructions for kitting, bundling and display builds.
  • Carriers and marketplaces publish packaging requirements that sellers must follow, which fulfillment staff turn into floor instructions.

Rights differ by owner. A brand's specification is the brand's; a 3PL's version of it may be derived content under a client agreement. See client-owned inventory rights in 3PL footage for the diligence questions, which apply to documents as well as video.

Fields that make a pack instruction usable

Most instructions mix free text with a few structured fields. Buyers benefit from records where the fields are explicit and consistent across SKUs.

Field groupExample contentWhy it matters for training or evaluation
Item identitySKU, GTIN, description, variantJoin key to video, images and catalog data
Dimensions and massNominal length, width, height, weightSupports carton selection; see the GS1 measurement attributes below
Container ruleCarton type, bag type, max items per boxDefines a correct outcome
Orientation and handling"This way up", fragile, keep dryStep constraint; handling symbols standardized in packaging practice
ProtectionVoid fill type, insert count, wrapDefines sequence and success criteria
Labels and documentsWhere the label goes, which to printOrdering and verification steps
ExceptionsHazmat flag, gift wrap, bundlesRare branches that video rarely covers

Two standards help you judge whether fields are defined consistently. GS1's Package and Product Measurement Standard covers nominal measurement attributes of products from consumer unit to pallet, and GDSN lets trading parties share product master data through GS1-certified data pools (GS1, 2026). ISO 780:2015 specifies graphical symbols conventionally used on distribution packages to convey handling instructions, and states that the symbols should be used only when necessary (ISO, 2015). A supplier whose records use these conventions will usually be easier to join to your other data. Neither standard defines a pack-out procedure, so check the supplier's own rule wording separately.

What this data can support, and what it cannot

Pack instructions can support:

  • Task specification. Ordered steps and constraints for a packing task, in language a vision-language model can use.
  • Labels for video. Mapping observed steps to intended steps, and flagging deviations.
  • Evaluation criteria. Pass/fail rules for a packed box: right carton, right fill, label placed, no overfill.
  • Planning inputs. Constraints for a task planner that sits above a manipulation policy.

They cannot support:

  • Control. No grasp, trajectory or force information. Whether a humanoid can fold a mailer around a soft item is learned from manipulation data, not from a rule sentence.
  • Perception of the actual item. A description of a bottle is not an image of that bottle. Pair with product catalog data for robot perception or purpose-captured images.
  • Ground truth for what workers really do. Written rules and floor practice often diverge, which is a reason to prefer instructions paired with footage.

Illustrative package: pack rules with linked video

# Illustrative only - synthetic values, not an available dataset
package: sku_pack_rules_v0
records: 4,000 SKUs (example scale chosen by the buyer, not a recommendation)
fields:
  sku_id, gtin, item_description
  nominal_dims_mm, nominal_mass_g
  carton_code, bag_code, max_units_per_carton
  orientation_rule, handling_symbols
  void_fill_rule, insert_rule, label_position
  exception_flags
linked_assets:
  video_clip_ids: where a recorded pack-out exists for the SKU
  image_ids: item and packed-state photos
versioning: rule_version, effective_date, superseded_by
rights: customer_account_id and permission flag per record

Version fields deserve attention. Packing rules change with carton stocks, carrier rules and client campaigns, so a clip from March may follow a rule that was replaced in June. Without effective dates, the video and the text can silently disagree.

Quality and acceptance checks

  • Sample 50 SKUs across categories and confirm each has complete required fields.
  • Check that identical products from different accounts do not carry conflicting rules without a stated reason.
  • Verify that units in dimension and mass fields are consistent.
  • Where video is linked, compare a sample of clips with the rule and record the match rate, so you know how closely floor practice follows documents.
  • Confirm that free-text instructions are in a language and format your annotators or models can parse.

Limitations and additional preparation

Instruction text is usually written for people who already know the building. Phrases like "use the usual box" depend on context a model lacks, so some records need rewriting or annotation. Coverage is also skewed: high-volume SKUs have detailed rules while long-tail items have none. Commercially sensitive details such as client promotions, discount packaging or customer-specific kits may be excluded by the owner. Plan for redaction of customer names and addresses in any example orders, and treat redaction as a separate step from permission.

Choosing between instruction records and recorded practice

Buyers sometimes ask whether to buy rules or footage first. Rules alone are cheap to process and carry the intended standard, but nothing shows how a person resolves an item that does not fit the rule. Footage alone shows practice but not the standard behind it. A small sample of both, joined by SKU, is often the most informative first purchase: it tells you how much floor practice departs from the written rule, and therefore how much weight to give each source in labeling.

If records come from several clients at a 3PL, check whether wording conventions differ, since one client's "fragile" may mean a different protection level than another's. Normalizing those into a common schema is annotation work and should be scoped before purchase.

For why 3PLs are a main source of these records, see 3PL providers as data suppliers.

Questions to ask suppliers

  1. Who authored the pack instructions: the brand, the 3PL or an ops team, and who owns them?
  2. How many SKUs have structured fields rather than free text only?
  3. How are rule versions and effective dates recorded?
  4. Do instructions reference GTINs or other identifiers that can join to images and video?
  5. What share of rules is exception-based, such as gift, fragile or hazardous-flagged items?
  6. Can you show a sample of instructions next to the recorded pack-out for the same SKU?
  7. Do any records include client-confidential promotions, customer names or pricing text?
  8. Are the same rules used across all sites, or does each facility keep its own?
  9. Which clients have agreed to licensing of their instruction records?

Discuss your requirements

If you need packing rules alongside video or catalog data, describe the SKUs, formats and permitted uses to SourceX. SourceX looks for US businesses that hold suitable material, checks the data and the supplier's licensing permissions, and coordinates the license and delivery. A request does not guarantee a match; SourceX follows up about potential sources. For the broader map, start at the humanoid training data guide or the warehouse and fulfillment hub. The site's page on SOPs and playbooks describes related document types, and dimensioning and weighing records cover the measurement side.

Discuss your humanoid training-data requirements with SourceX

Sources

Frequently asked questions

What do SKU-level pack instructions contain, and who holds them?

SKU-level pack instructions are structured text stating how each item should be packed, including carton choice, orientation, void fill, inserts, labels and handling marks. Brands, 3PLs, contract packagers and carriers hold versions of them, and rights differ by owner.

Why do pack instructions help when judging whether packing video was done correctly?

Packing video shows what a worker did, not what the worker was supposed to do. Pack instructions supply the intended rule for each item, which lets a buyer check the video against it, label steps and write evaluation criteria.

What can pack instructions not support for a humanoid packing task?

They contain no grasp, trajectory or force information, so whether a humanoid can fold a mailer around a soft item is learned from manipulation data rather than from a rule sentence. A written description of a bottle is also not an image of that bottle, so instructions need pairing with catalog or purpose-captured images.

Describe the data your robots need

Describe the tasks, modalities and permitted uses you need. SourceX reviews the requirement and follows up about potential sources; a request does not guarantee a match.

Discuss your humanoid training-data requirements with SourceX
See if you qualify