Why Products exists
A product record becomes operational long before someone opens a detail page. Search depends on identifiers. Fulfillment depends on components, substitutes, and package data. Shopify synchronization depends on the right product mapping. When those facts are incomplete or duplicated, the problem usually appears later as an ambiguous scan, an unfillable order, or a bad shipment measurement.
Products gives that work a dedicated OMS app: a searchable product workbench, an operational product-detail workspace, and data-quality queues for records that need attention.
Find and organize the catalog
The workbench searches product names and configured identifiers, including SKU and UPC, and filters results by product type, product store, and tag. Users can select multiple products and add tags in one action, then open a product without losing the context of its family or variants.
Maintain the record fulfillment uses
Product detail brings together the fields and relationships available in the June app: product family and variant navigation, configured identifiers, components, substitutes, tags, categories, prices, features, inventory policy, and Shopify shop-product mappings. The app supports creating a product as well as editing an existing one.
Shipping and handling has its own section for box type, width, height, depth, weight, and their units. A 3D box preview updates from those values and normalizes different length units, making an implausible package shape easier to catch before the data is used for fulfillment.
Turn data quality into a queue
Duplicate Identifiers groups products that share the same configured identifier value and lets an operator resolve the conflict. Missing Values shows field coverage and drills into the affected products for the selected rule. These are explicit work queues, not quality problems that have to be discovered indirectly through another system.
Product change history shows recent field-level changes on the record. Imports shows the latest product import entries and can be searched by product, SKU, barcode, or Shopify shop. Together, those views give operations a starting point when a product changed or an import did not produce the expected result.
One product workspace, fewer indirect investigations
The value of Products is not another place to store product data. It is that the relationships, fulfillment measurements, external mappings, and quality issues the June app actually supports can be found and corrected from one product-focused workspace.
