Basic Concepts and Data Structure
SUMMARY
Delivery date and time settings are made per group. Group 1 = Standard (the default for products with no link). A group can have slots (the options of the delivery method).
ENTITIES
group: # internal name: pattern
ui: Settings → Group Management
key: group number (1 = Standard)
has: priority (smaller = higher priority), name, a full set of date/time settings
note: settings are independent between groups (holidays and so on are not shared)
slot: # an option of the delivery method. A group can have several
ui: Settings → Delivery method is Active
has: title, a full set of date/time settings (separate for each slot)
product_link: # link between products and groups
- specified per product in Products Management
- specified with product tags (tag name → group). "tag::SKU" for a single variant
- selected by conditions (weight / total price / stock quantity)
- none of them → Group 1UI_LABELS
Left menu: Settings / Products to be Hidden / Style / Online Store / Option / Connect(Pro Plan) / CSV / Notification. Buttons at the top of the screen: “Add Tags”, “Contact”.
| Concept | Where in the admin and field name | Setting key (internal) |
|---|---|---|
| Hide the date | Settings → card “Delivery Date” → “Delivery Date is Inactive” | display.date |
| Hide the time | Settings → card “Delivery Time” → “Delivery Time is Inactive” | display.time |
| Display label | “Label Text” of each card | label.date / label.time |
| Shortest date | “Minimum Delivery Date: [ ] days after order” | rangeDate.start |
| Calendar days | “Setting the Minimum Delivery Date as the combination of business days and calendar days.” → “Calendar Day” | rangeDate.calStart |
| Longest date | “Maximum Delivery Date: [ ] days after order” | rangeDate.end |
| Count from the shortest date | “Calculate Maximum Delivery Date from Minimum Delivery Date” | rangeDate.endAs |
| Cut-off | “Cut off time” (Not Applicable / 0:00 to 23:00) | cutOffTime (99 = not applied) |
| Holidays | “Holidays” under the shortest date (weekday checks + calendar) | holidays / holidayWeeks |
| Blockout dates | “Blockout Date” (weekday checks + calendar) | dates / disableWeeks |
| Selectable dates only | With “Only on Specified dates” ON, “Blockout Date” becomes “Specified date” | rangeDate.valid |
| Adjustment of the shortest date by area | “Determine the Minimum Delivery Date based on selection preferences, such as the delivery area.” | selectDays / label.area |
| Required date | “Required field to [Delivery Date]” (“Placeholder” / “Alert Message”) | essentials.activeDate |
| Required time | “Required field to [Delivery Time]” (first selection / “Alert Message”) | essentials.activeTime |
| Time options | The list in the card “Delivery Time” and “Add” | times |
| Detailed time settings | “Activate advanced delivery time settings (for same-day pick-up at restaurants, etc.)” | timesDetail |
| Delivery method (slot) | Card “Delivery method” → “Delivery method is Active”, “Add” | slotDisplay / slotOpts |
| Grouping products | Card “Targeted products” → “Products Group is active” | patternChecked |
| Group management | Card “Products Group” → “Group Management”, “Add” | patterns |
| Priority | The up/down buttons of “Priority” | priority |
| Selection conditions | “Selected Conditions” → “Conditon is active” (weight / price / stock) | conditions |
| Linking by tags | “Products Management” → “Product tags for individual product settings is active.” | productsControlTags / productsTags |
| Hidden products | “Products to be Hidden” → “Hidden” in the product list | productsNoDisplay |
| Hidden has priority | “In the presence of multiple items in the cart, prioritize ‘Hidden’ is active.” | productsNoDisplayUsual |
RULES
C-1 Group 1 is the Standard group and cannot be deleted. A product with no link always becomes Group 1.
C-2 Group settings are independent. The blockout dates of Group 1 are not reflected in Group 2.
C-3 The smaller the priority number, the higher the priority.
C-4 When there are slots, the date/time settings are held per slot.
C-6 When a group is deleted, the product links, tag settings and shipping method customization settings for that group disappear too, and the affected products fall back to Group 1.
C-5 The special product-tag form "tag name::SKU" links only the variant with that SKU to the group.
C-7 The widget writes the delivery date and time to the cart attributes, and in the order they become the "additional details" (order.customAttributes). This is where they are saved first (L-13 in 085 / TS-1 in 080).
C-8 The key of an "additional details" entry is the same as the display label in the admin (delivery date, delivery time, etc.). If you change the label, the key changes too (TS-1). The value is, for the date, the format of "Inputed Date Format" in "Settings for Calendar" (default depends on the admin language; D-5 in 040), and for the time, the text of the selected time option.
C-9 With Pro "integration", the key of the "additional details" entry (the label for integration) and the date/time format can be set separately from the display label. The initial values per integration target are in the table in 130 (e.g. NextEngine: delivery_date / YYYY/MM/DD). The date and time can also be combined into one value (K-5 in 130).
C-10 To also put them into order metafields, the order note or order tags, use "Write to orders automatically" under "Option" (Shopify Flow is required; PROC-O2 in 070). For metafields, specify a namespace and key (defaults: custom.delivery_date / custom.delivery_time). The type is date or text (a date type is year-month-day).
C-11 The "Order Metafields" in the CSV export (Pro; 090 / 100) reads metafields that already exist on the order into CSV columns. It is not a feature that writes the delivery date and time into metafields.QA
- Q: What is a group? A: The unit for changing the delivery date and time settings per product. The default is Group 1. You link products to groups to use them.
- Q: Can customers choose a different delivery date for each product? A: No. One order carries one delivery date and time (R7).
- Q: How are the delivery date and time saved in the order? What are the key names and value formats? Can they be saved to order metafields? A: They are first saved in the order’s “additional details” (customAttributes), with the key = the display label and the value = the date (in the “Inputed Date Format”) or the time option text (C-7, C-8). To also put them in metafields, use “Write to orders automatically” under “Option” (Shopify Flow is required) (C-10). With Pro integration, the key and format can be matched to the integration target (C-9). Concrete example keys (default labels) depend on the “display label” setting in the admin. CSV variables (such as order.date) are names for CSV export, not the actual keys.
- Q: What is the difference between a slot and a group? A: A group is the unit of per-product settings; a slot is an option of the delivery method inside the same group (delivery / store pickup, etc.).
ESCALATE
- A field in the admin cannot be found: check the plan (Normal / Pro) and the app version display.
SEE
