Bundle data: retain component quantities and revisions
Connect a bundle to its components, quantities and reviewed revisions. An Alton Goods industry reference for a structured product-data handoff.
Cin7’s customer story describes Alton Goods selling combination products whose individual components could run out while the combination remained available to buy. The owner reports using Cin7 Core’s Bill of Materials so that a depleted individual item makes the combination show no remaining stock. This is a software-provider publication with customer testimony. It does not disclose the component lists, required quantities or substitution rules for particular bundles. PandaBuyNow did not deliver this project.
Record the relationship behind each bundle
For a Chinese marketplace data brief, PandaBuyNow proposes keeping the observed selling item separate from the components needed to describe it. Record the bundle’s source URL, visible identifier and selected configuration. Give each component its own row with a source reference, identifier, required quantity and unit where the source establishes them.
Keep the relationship’s revision or observation date with those rows. A supplier’s bundle code, your recipient’s internal SKU and a component code may each identify a different object. Preserve that distinction when preparing the file. Leave a missing component quantity unresolved instead of inferring it from a photograph.
Try a fictional change to the component requirements
Consider an invented selling item, LIGHT-KIT-A. Review version A lists one LAMP-A and two BAT-A units. A later source description names BAT-B, but does not state whether the required quantity has changed. Retain version A and create a separate unresolved change record for the later description.
The recipient’s designated reviewer can assess the component identity, quantity and applicable bundle version. An approval to use BAT-B should state which relationship it changes. These labels and quantities are fictional; they describe no Alton Goods or PandaBuyNow order.
Agree what the handoff can establish
Review a sample containing one complete bundle relationship, one missing quantity and one proposed component change. Confirm that the recipient can distinguish an observed composition from an approved mapping and can trace each decision to the reviewed version. A component change should leave its unresolved questions visible.
Record any visible availability statement with its source and observation time. The worksheet supports review of collected material; deciding whether stock is available for a new order requires its own current operational evidence. For a PandaBuyNow discussion, bring representative marketplace links, the bundle relationships you need to understand and the recipient’s expected format. Agree feasible fields, review responsibilities and delivery scope through a sample.
PandaBuyNow’s deliverable is the agreed product, listing or variant dataset in JSON or CSV, with field definitions, source references and data-quality notes.