Packing, production, label, and material lists use each order's provider department time zone for delivery times and delivery-date grouping. Expected delivery time takes precedence over desired delivery time. Without a provider department or a resolvable department time zone, system time is used.
Shared PDF page headers and sales-list print timestamps and range boundaries use department local time when a single department is known. Delivery dates supplied to page headers are already local dates.
Sales-summary PDFs and production lists (PDF and Star markup) share the same summary configuration:
| Parameter | Values | Meaning |
|---|---|---|
product_summary_grouping |
product_first, component_first |
Product totals followed by their choices, or component requirements followed by references to the products using them. |
ingredient_details |
within_groups, separate_summary, hidden |
Place ingredient choices within the groups, in a separately headed summary, or omit their details. Category sections retain their own ingredient summary. |
Ingredient requirements include the parent-quantity multiplier. Acquisition quantities are independent additional purchases and remain visible when ingredient details are hidden or summarized separately. Variations remain visible, including the implicit variation of a grouped product with one ingredient group. Normal and Child backing-product types do not determine ingredient-detail placement. Standalone sales of a component remain distinct from component requirements.
Each parent order line contributes to one product total. Component-first parent references can repeat across components; their labels identify them as references, and they carry no price. Product amounts include their selected choices and acquisitions using the stored order-line total. Component details and the separate ingredient summary carry no additional price and never increase the subtotal. This subtotal is the included order-line total, not shipping or order-level rebates.
Grouped products appear as tagged group headings/subtotals with no displayed quantity; their order-line count is not a count of selected products. Selected variations carry a choice tag and their effective quantities, including single ingredient-kind groups normalized to variations. Ingredient details and acquisitions retain distinct component and acquisition tags. No combined child quantity is inferred for the group.
This hierarchy covers choices stored in selected_variants; legacy children stored as separate order lines are not reconstructed into the group.
PDF tags use smaller regular text aligned to the name's baseline; Star markup uses plain brackets. In component-first output, indented "Of these, quantity for product" descriptions distribute the component/choice/acquisition quantity above across its parents, not the parents' sold quantities. These descriptions have no separate quantity cell or amount. Group and ordinary-product amounts are counted once on their total rows. One legend per report explains only the kinds present. Wrapping reserves space for the PDF tag; exceptionally narrow cells fall back to wrapped inline text rather than clipping. The report omits a separate explanatory price footnote.
Product-first grouping with ingredient choices in the main overview is the default in discovery, requests and saved formats without explicit settings, for both PDFs and Star markup. Explicit component_first settings retain the alternative layout. An explicit ingredient_details takes precedence over legacy parameters: show_customizations=false maps to hidden and true to within-groups; an explicitly enabled sales-summary show_summary_of_variants maps to separate-summary and false to within-groups. The legacy switches are not exposed alongside the shared settings.
The production table uses a separate matrix builder and does not expose these grouping controls.