Orders & fulfilment

What Flare writes on your orders

Updated 19 August 2026

Every scheduled order carries its dates in three forms: order tags, order attributes, and line-item properties. Your team, your searches, and your other tools can all read the promise.

Tags

Tag	Example	Meaning
Delivery date	`Delivery on Jan 15 2025`	The date the customer chose
Ship date	`Ships on Jan 13 2025`	The dispatch date Flare calculated
Pickup date	`Pickup on Jan 15 2025`	The collection date on a pickup order
`pickup`	`pickup`	Marks a Shopify pickup order. The collection location follows as its own tag
`Ready to Ship`	`Ready to Ship`	Added when the order comes within your dispatch window. See hold & release
`Flare`	`Flare`	Added when hold and release is on, so the release job can find the order
Time slot	`Time slot: 9am-12pm`	Added when the customer chose a time slot

Orders can also carry the shipping profile and zone names, Mixed delivery dates when the cart splits across dates, and No date allocated when the customer chose "no date".

Tags make Shopify's order list filterable by date. The View all orders, View unfulfilled, and View fulfilled links on Order management are exactly these tag filters.

Choose what Flare writes

Open Order management → Settings and find Fulfilment attributes & tags. Three toggles decide what each order carries:

Add delivery date attribute & tag
Add ship date attribute & tag
Add pickup date attribute & tag

Turn the pickup toggle on and pickup orders keep their date in their own attribute and tag. Turn it off and they reuse your delivery and ship settings instead.

Under each toggle, a summary line shows the tag and the attribute key in use. Click the summary to change them:

Custom attribute key: rename the attribute when another system expects a different key.
Attribute value format: ISO 2025-01-15 (the default), US 01/15/2025, UK 15/01/2025, Jan 15, 2025, and more.
Tag format: set the Text before date prefix ("Delivery on", "Ships on", or nothing) and the Date format after it. A preview shows the finished tag.

Changing formats is safe mid-flight. Flare reads both old and new formats on existing orders.

For the full tour of that tab, see the Order management Settings tab.

Order attributes

Order-level attributes carry the machine-readable values:

__flare_delivery_date, __flare_ship_date, __flare_pickup_date, __flare_time_slot
Shipping context when zones are on: __flare_shipping_profile and __flare_shipping_zone_name

These attributes power the order confirmation email snippet and the thank-you and order status displays. Product and cart page setups also write a line-item property, labelled Estimated Delivery by default, visible on the order's line items. Rename it on Storefront experience.

Shopify "Fulfill by"

Flare writes the ship date into Shopify's native Fulfill by field on the fulfilment order, so the deadline shows in Shopify's own order list with no extra apps. It is on by default. If another integration owns that field, open Order management → Settings and switch off Sync ship date to Shopify "Fulfill by", which sits under the ship date toggle.

Using it all in Shopify Flow and other apps

Because dates are ordinary tags and attributes, anything that reads orders can act on them:

Shopify Flow: route rush orders ("tag contains today's ship tag"), notify a channel, or add fulfilment holds of your own.
Flow trigger: Flare fires a delivery date changed trigger when a customer reschedules. Build "notify the kitchen" automations on it. See self-serve rescheduling.
3PLs and OMS: ShipStation gets first-class sync (guide). Anything else can key off the tags, the attributes, or Fulfill by.