> ## Documentation Index
> Fetch the complete documentation index at: https://docs.florists.digital/llms.txt
> Use this file to discover all available pages before exploring further.

# Repeat Orders

> Automatically create orders for customers who need flowers on a regular schedule.

Some customers need flowers regularly — a hotel that wants fresh reception flowers every Monday, a church that needs an arrangement on the first of every month, or an office that gets a bouquet delivered every other Friday. Instead of creating these orders manually each time, you can set up a **repeat order** and let Digital Florists handle it.

Repeat orders are included with Orders.

## How it works

You create the first order as normal — pick the customer, add the products, set the address and fulfilment method. Before you submit, tick the **Repeat Order** box and tell it how often. From then on, a new order is created automatically each time one is due.

Each generated order is an exact copy of the original — same products, same quantities, same prices, same address. It appears in your order list as **Unconfirmed**, ready for your team to review and prepare, just like any other order.

## Setting one up

<Steps>
  <Step title="Create the order as normal">
    Go through the usual [order creation process](/daily-operations/creating-an-order) — pick the customer, add the products, and set the fulfilment method (delivery or collection).
  </Step>

  <Step title="Tick the repeat box">
    Before you submit, tick **Repeat Order**. A new panel appears where you set the schedule.
  </Step>

  <Step title="Pick the schedule">
    Choose how often the order should repeat:

    <AccordionGroup>
      <Accordion title="Every week (or every 2 weeks, 3 weeks, etc.)">
        Select **Weekly** and click the days you want — for example, Monday and Thursday. Set "every 1 week" for weekly, "every 2 weeks" for fortnightly, and so on.
      </Accordion>

      <Accordion title="Every month (or every 2 months, 3 months, etc.)">
        Select **Monthly** and enter the day of the month — for example, the 1st or the 15th. If you pick the 31st and a month only has 30 days, it uses the last day of the month instead.
      </Accordion>

      <Accordion title="Every day (or every 2 days, 3 days, etc.)">
        Select **Daily** and set how many days apart — every 1 day, every 2 days, etc.
      </Accordion>

      <Accordion title="Specific dates">
        Select **Specific Dates** and add the exact dates you want — for example, 14 Feb, 10 Mar, 30 May. Useful for customers who know exactly when they need flowers.
      </Accordion>
    </AccordionGroup>
  </Step>

  <Step title="Set how far in advance to create it">
    The **Create Before** field sets how many days before the fulfilment date each order is created. This gives you and your team time to prepare.

    For example, if the fulfilment date is Monday and you set this to **5 days**, the order appears on your dashboard on the previous Wednesday.

    <Tip>
      Most shops set this to **3–5 days**. That's enough notice to order stems and prepare without cluttering your order list too far ahead.
    </Tip>
  </Step>

  <Step title="Set when it starts and ends">
    Pick a **start date** for the schedule. If the customer wants flowers indefinitely, leave the end date blank. If it's a fixed contract (say, 6 months of weekly flowers for a hotel lobby), set an end date.
  </Step>

  <Step title="Submit the order">
    Submit the order as normal. The first order is created straight away, and Digital Florists takes care of the rest.
  </Step>
</Steps>

## What happens each time an order is due

Every morning at 8am, Digital Florists checks whether any repeat orders need creating. When one is due, it:

1. Creates a copy of the original order with the same products, prices, and address
2. Sets the order status to **Unconfirmed** so your team can review and prepare it
3. Sets the payment status to **Unpaid** — unless the customer is on an account (see below)
4. Sends your team a worksheet notification so they know what to make
5. Triggers any [automations](/settings/automations) you have set up for new orders

For **account customers** (hotels, corporates, etc.), the payment status is automatically set to **Paid** and the order is added to their account for invoicing. For everyone else, your team collects payment as normal.

<Tip>
  For customers who pay by bank transfer, set the payment method to **Pay on Fulfilment** when creating the repeat. This keeps each generated order marked as unpaid until you've confirmed the transfer has arrived. Add an order note like "Check bank transfer has been paid" so your team remembers to verify before sending the flowers out.
</Tip>

<Warning>
  Repeat orders keep their **own prices** — changing a product's price in your catalogue, or on one already-created order, does not change what future repeat orders charge. To change what a repeat charges going forward, open it and click **Update Repeat Order**.
</Warning>

## Managing your repeats

Go to **Orders** > **Repeat Orders** to see all your repeats in one place.

### What you'll see

Each repeat order shows you:

* Whether it's **active** or **paused**
* The **upcoming fulfilment dates** (up to 10)
* A history of **every order** generated from this repeat
* The **customer** it belongs to
* Any **errors** from the last generation attempt (with a count of consecutive failures)

### Changing the products or prices

Open the repeat order and you'll see its **Products** list below the schedule — the products, quantities, and prices that future orders will be created with. To change them, click **Update Repeat Order**. This opens the normal order form, pre-filled with the repeat's products, prices, customer, address, notes, and schedule — exactly the screen you use for any order. Make your changes there and submit.

When the update completes, the current repeat is ended and a new one takes over from the next scheduled date. Everything already created stays exactly as it was.

<Note>
  Because this uses the full order form, you have complete control — messages, notes, delivery details, everything — not just prices. If you only need to adjust one specific upcoming order (say, an upgrade for one week only), edit that generated order directly instead of updating the repeat.
</Note>

### Changing the schedule

For an active repeat, you can change anything about the schedule — the days, how often, or when it ends. Changes only affect future orders; ones that have already been created stay as they are.

### Pausing

Customer going on holiday? Toggle the **Pause** switch. New orders stop being created until you switch it back on. Nothing is lost — it picks up where it left off.

### An extra order outside the schedule

If a customer rings up wanting an extra order outside their usual schedule, create it as a new one-off order. The fastest route is to search for the customer when starting the order and use the **Re-order** option against one of their previous orders, which copies their products across so you only need to set the date and any extras. Repeats only generate orders on their own schedule.

## Turning off notifications for repeat orders

By default, the same customer notifications fire on a generated repeat order as on any other order — order created, dispatch, and so on. Two ways to stop them.

* **Order level** — on the original order, tick **Disable notifications** before you submit. Every order generated from that repeat is created with notifications disabled too.
* **Customer level** — on the customer's profile, tick **Opt out of notifications**. That silences operational notifications for every order placed for that customer, repeat or otherwise.

For the difference between the two, and how overrides interact with opt-outs, see [Recipients](/settings/notifications-recipients#order-type-rules-advanced).

## When something goes wrong

Repeat orders rarely fail to generate. The alerts in this section are a precaution for the odd case where something blocks generation (the customer's been removed, or their address is missing). When that happens:

* You'll see a **red alert on your dashboard** telling you how many repeats have problems
* Digital Florists tries again the next day
* If it fails **5 times in a row**, the repeat is **paused automatically** so it stops cluttering your error list until you fix the underlying problem

### Sorting it out

1. Go to **Orders** > **Repeat Orders** and look for the ones marked in red
2. Read the error message; it tells you what's wrong
3. Fix the problem (e.g. add the missing address back)
4. In the row's actions menu, click **Retry** to generate the order now
5. Or click **Test** to walk through the generation without creating an order — useful for confirming your fix worked before you commit to it

If the error doesn't make sense or you can't get the repeat going again, [get in touch with support](/get-started/getting-help). These failures are uncommon enough that we'd rather hear about it than leave you stuck.

<Note>
  **Retry** and **Test** only show on the Repeat Orders list, against repeats that are currently failing or paused, not on the individual repeat order page.
</Note>

## What gets copied (and what doesn't)

Each new order is an exact copy of the original:

* Same products and quantities, at the original prices
* Same custom items (like "Florist's Choice — £40")
* Same address and fulfilment method (delivery or collection)
* Same fulfilment charge

Things that **don't** carry over:

* Delivery run assignments — you assign each generated order to a run as normal
* Promotions or discount codes — these aren't reapplied automatically
* External references from integrations (e.g. Shopify order IDs)

## Repeat tasks

There's a similar feature for **tasks** — things your team needs to do regularly. Common ones:

* "Clean the cooler every Monday"
* "Order weekly stock every Wednesday"
* "Water the shop display every 2 days"

Repeat tasks have two extra options: **Skip if Closed** (don't create the task on days your shop is closed) and **Keep Assigned User** (so each generated task is assigned to the same team member as the original).

Go to **Tasks** > **Repeat Tasks** to set them up. See [Repeat Tasks](/daily-operations/repeat-tasks) for the full guide.

## Common questions

<AccordionGroup>
  <Accordion title="Can I change the products on a repeat order?">
    Yes. Open the repeat order and click **Update Repeat Order** — the order form opens pre-filled with the current products, prices, and schedule for you to change. On submit, the old repeat is ended and the updated one takes over from the next scheduled date. Changes apply to future orders only; ones already created stay exactly as they are.
  </Accordion>

  <Accordion title="What happens if I delete the original order?">
    The repeat keeps working. Each generated order is independent, so deleting the original doesn't stop future ones from being created.
  </Accordion>

  <Accordion title="Can I set up a repeat for a collection?">
    Yes. Repeat orders work for both deliveries and collections.
  </Accordion>

  <Accordion title="Can I set up a repeat for a relay order?">
    No. Relay orders (e.g. Direct2Florist) need a different florist to accept and fulfil each one, so they can't be automated.
  </Accordion>

  <Accordion title="When exactly does the order get created?">
    Digital Florists checks every day at 8am. Orders are created based on the **Create Before** days you set — so if you set 5 days and the fulfilment date is Monday, the order appears on the previous Wednesday.
  </Accordion>

  <Accordion title="Will prices update if I change my product prices?">
    No. Repeat orders use the prices from when they were first set up. If you want to charge the new price, edit the repeat order.
  </Accordion>

  <Accordion title="Can a customer have more than one repeat order?">
    Yes. You can have as many as you need — for example, a hotel might have weekly reception flowers and monthly restaurant table arrangements as separate repeats.
  </Accordion>

  <Accordion title="What about months with fewer days?">
    If you set a monthly repeat for the 31st and a month only has 30 days, Digital Florists creates it on the 30th. For February, it uses the 28th (or 29th in a leap year).
  </Accordion>

  <Accordion title="How do I stop a repeat order permanently?">
    Set an end date, or delete it from the Repeat Orders page. Deleting a repeat doesn't delete orders that have already been created.
  </Accordion>

  <Accordion title="Do customers get notified each time?">
    Yes, by default — generated repeat orders fire the same notifications as any other order. To silence them, tick **Disable notifications** on the original order or **Opt out of notifications** on the customer. See [Turning off notifications for repeat orders](#turning-off-notifications-for-repeat-orders).
  </Accordion>
</AccordionGroup>

## What's next?

<Columns cols={2}>
  <Card title="Creating an Order" icon="plus" href="/daily-operations/creating-an-order">
    Walk through creating your first order step by step.
  </Card>

  <Card title="Orders" icon="clipboard-list" href="/daily-operations/orders">
    Learn about managing orders day to day.
  </Card>

  <Card title="Tasks" icon="list-check" href="/daily-operations/tasks">
    Set up recurring tasks for your team.
  </Card>

  <Card title="Notifications" icon="bell" href="/settings/notifications">
    Control what customers are told when orders are created.
  </Card>
</Columns>