Free OpenClaw Skill for Bakeries: Custom-Order and Wholesale Agent (Download)

What this skill does for your bakeries

• Triages custom cake inquiries by category (smash, tiered, sculpted, wedding) and enforces lead-time minimums with a gentle alternative offer rather than a flat no.
• Compiles the weekly decorator-hours forecast from Square for Retail, BakeSmart, Cybake, or FlexiBake exports, flagging the days that overrun capacity before the order is accepted.
• Runs wholesale standing-order confirmations for cafes, hotels, and grocery accounts on a daily cutoff cadence with delivery-route awareness.
• Drafts deposit reminders, day-of pickup nudges, and tasting follow-ups for wedding-cake leads on a 7, 21, 60-day cadence.
• Flags cottage-food vs commissary vs licensed-bakery jurisdiction for any inquiry that crosses state lines, with the FDA cottage-food rule applied to the customer's address.

What's inside this OpenClaw skill

The full file you download, indexed below for search engines and for operators who want to read before they install.

---
name: bakery-custom-order-and-wholesale
description: Custom cake intake, wholesale standing-order coordination, decorator calendar capacity, and cottage-food jurisdiction routing for bakeries. Integrates with Square for Retail, Toast, BakeSmart, Cybake, FlexiBake.
version: 1.0.0
author: OpenClaw Consult (Adhiraj Hangal)
license: MIT
url: https://openclawconsult.com/skills/bakeries
---

# OpenClaw Skill: Bakery Custom-Order and Wholesale Coordinator

## Overview

This skill turns the OpenClaw agent into the custom-order and wholesale
coordinator for a working bakery. It owns the 2 a.m. custom-cake inquiries,
the daily wholesale standing-order confirmations, the decorator-capacity
forecasting, and the cottage-food jurisdiction check that the owner usually
does by gut. The front-counter staff still hand the cake across the counter
and do the wedding tasting. The agent absorbs the repetitive intake.

Designed for 1 to 3 location neighborhood bakeries with 1 to 6 decorators
and a wholesale book in the $5k to $80k per month range. Single-unit and
small multi-unit both work.

## What this skill does

1. Custom-cake inquiry triage with lead-time enforcement and gentle redirect
2. Decorator-hours forecasting for the upcoming week with overcapacity alerts
3. Wholesale DSD daily cutoff confirmations for cafes, hotels, grocery accounts
4. Deposit reminders and pickup nudges for booked wedding and tiered orders
5. Tasting follow-up cadence at 7, 21, 60 days for wedding-cake shoppers
6. Cottage-food vs commissary vs licensed-bakery jurisdiction flagging

## Triggers

```yaml
triggers:
  - type: heartbeat
    schedule: "0 6 * * *"            # Daily 6am, before the morning shift
    action: morning_custom_order_review

  - type: heartbeat
    schedule: "0 17 * * *"           # Daily 5pm, wholesale cutoff
    action: wholesale_standing_order_confirm

  - type: heartbeat
    schedule: "0 7 * * 1"            # Mondays 7am
    action: compile_decorator_hours_forecast

  - type: on_event
    event: pos.custom_cake_inquiry_submitted
    action: triage_inquiry_and_draft_reply

  - type: on_event
    event: pos.wedding_tasting_completed
    action: enter_tasting_followup_cadence

  - type: on_event
    event: pos.deposit_due_window_open
    action: send_deposit_reminder
```

## Workflow: custom-cake inquiry triage

When a custom-cake inquiry hits the website form, email inbox, or POS, the
agent:

1. Classifies the request: smash, tiered (2 or 3 tier), sculpted, wedding, cupcake tower, novelty
2. Checks the requested delivery date against the lead-time matrix
3. Pulls current decorator hours for that week
4. If the inquiry fits, drafts a confirmation with deposit link and design intake form
5. If the inquiry violates lead-time, drafts a gentle redirect with an achievable buttercream alternative or the next available date
6. Routes everything to the owner for approval (autonomous on standard lead-time confirmations after two weeks)

The skill defaults to never auto-confirming a wedding tasting or a deposit-required order. Those always route to a human.

## Workflow: decorator-hours forecast

Every Monday at 7am the agent:

1. Pulls every confirmed custom order for the upcoming 14 days
2. Estimates decorator hours per cake from the category matrix
3. Rolls up daily totals against decorator capacity from the config
4. Flags any day that exceeds 90% capacity as warning, 100% as block
5. Drafts a forecast summary for the owner with the specific cakes pushing the day over

The default capacity matrix:

```yaml
decorator_hours_per_cake:
  smash: 1.0
  birthday_simple: 2.0
  birthday_themed: 3.5
  tiered_2: 5.0
  tiered_3: 8.0
  sculpted_character: 10.0
  wedding_per_tier: 4.0
  sugar_flower_addon: 3.0
  cupcake_tower_24: 2.0
  cupcake_tower_48: 3.5
```

A representative single-location bakery with 2 decorators runs a 64-hour
weekly capacity. The skill flags the days that overrun before the next
inquiry pushes them past the line.

## Workflow: wholesale DSD daily cutoff

Every weekday at 5pm the agent:

1. Pulls the standing orders for the next morning's delivery
2. Reconciles against the production sheet
3. Drafts the confirmation message to each account contact
4. Flags any standing-order quantity that exceeds the production plan
5. Logs the route to the morning driver's manifest

Cafes, hotels, and grocery accounts each get their account-specific format. The skill never auto-adjusts a wholesale price; price exceptions always route to the owner.

## Workflow: wedding-cake tasting follow-up

After a tasting is logged, the agent enters the lead into a 7, 21, 60-day cadence:

- Day 7: warm thank-you with one personalized detail from the tasting
- Day 21: doctor-voice (baker-voice) differentiation note: your flour, your fillings, your sugar-flower work
- Day 60: case-study or recent-wedding social proof

Tasting-to-booking conversion in a typical neighborhood bakery is in the
30 to 45% range. With this cadence in practices we have scoped, it tends
to lift to the 48 to 58% range over a quarter.

## Workflow: cottage-food jurisdiction routing

When an inquiry comes from outside the home state, the agent:

1. Looks up the originating state's cottage-food rule
2. Looks up the home state's commissary and interstate-shipping rule
3. If the order would force a cottage-food violation (e.g., shipping wedding cake across state lines from a cottage-food kitchen), flags the conflict with the specific FDA or state-DA rule cited
4. If the order is clean, proceeds to the standard intake

The matrix is editable in the config block. We ship the current 50-state
matrix as a starting point and stamp it with the last-reviewed date so the
owner knows when to refresh.

## Message templates

```yaml
templates:
  custom_order_within_lead_time:
    subject: "Yes, we can do {cake_type} for {requested_date}"
    body: |
      Hi {customer_first_name},

      Yes, we can do {cake_type} for {requested_date}. Quick recap on what
      I have from your inquiry:

      {inquiry_summary}

      To lock the slot in the decorator calendar, here is the design intake
      form: {intake_form_url}

      The non-refundable deposit for this category is {deposit_amount}, due
      within 48 hours to hold the date.

      Reach back any time. We are excited to make this for you.

      {bakery_name}

  custom_order_lead_time_redirect:
    subject: "About {requested_date} for your {cake_type}"
    body: |
      Hi {customer_first_name},

      Thank you for thinking of us for {cake_type}. {requested_date} is
      inside our {minimum_lead_time} window for {technique}, which means we
      cannot do justice to the original design in that timeline.

      Two options I would love to walk through:

      1. We can do a {alternative_design} version of this cake by
         {requested_date}, which uses {alternative_technique} and would
         absolutely be ready.
      2. We can build the original design exactly as you described for
         {next_available_date}, which is the next slot in the decorator
         calendar.

      Reply with whichever works for your family and I will hold it.

      {bakery_name}

  wholesale_daily_confirmation:
    subject: "Tomorrow's delivery: {account_name}"
    body: |
      Hi {account_contact_first_name},

      Confirming tomorrow's delivery for {account_name}:

      {standing_order_list}

      Driver: {driver_name}
      ETA: {delivery_eta_window}

      Any swaps or pauses, reply by 6pm tonight.

      {bakery_name}

  tasting_followup_day_7:
    subject: "Thinking about you and your {wedding_or_event}"
    body: |
      Hi {customer_first_name},

      Loved the tasting last week. I keep thinking about how you described
      wanting {personalized_detail}. We have a moment open to chat through
      the design direction whenever you are ready.

      No pressure, but if you want to put a hold on {tasting_date_recommendation},
      reply with a yes and I will block the decorator hours.

      {bakery_name}

  wedding_deposit_reminder:
    subject: "Your deposit window for {wedding_date}"
    body: |
      Hi {customer_first_name},

      Just a friendly heads-up: the deposit window for your {wedding_date}
      cake closes in 48 hours. The amount is {deposit_amount}, and you can
      drop it via {deposit_link}.

      Once the deposit lands we lock the date in the decorator calendar.

      Reach back any time.

      {bakery_name}

  cottage_food_jurisdiction_flag:
    channel: slack
    body: |
      COTTAGE-FOOD JURISDICTION CHECK
      Inquiry from: {customer_state}
      Cake type: {cake_type}
      Conflict: {jurisdiction_rule_cited}
      Suggested response: {drafted_response}
```

## Memory keys

```yaml
memory:
  - key: bakery.custom_order_status[{order_id}]
    description: Stage of the custom order through intake, deposit, production
    values: [inquiry, lead_time_check, deposit_pending, confirmed, in_production, ready, completed, cancelled]

  - key: bakery.decorator_capacity[{date}]
    description: Estimated decorator hours used and capacity remaining for the date
    schema: { hours_used: number, capacity: number, status: string }

  - key: bakery.wholesale_account[{account_id}]
    description: Standing order pattern, delivery route, contact preferences
    schema: { weekly_pattern: object, route: string, contact: string, last_confirmed: date }

  - key: bakery.tasting_lead[{lead_id}]
    description: Wedding-cake tasting lead stage in followup cadence
    values: [tasted, day_7_sent, day_21_sent, day_60_sent, booked, lost]

  - key: bakery.cottage_food_matrix
    description: 50-state cottage-food rule reference, last reviewed date
```

## Required integrations

| Integration              | Purpose                                          | Read | Write |
|--------------------------|--------------------------------------------------|------|-------|
| Square for Retail        | Items, modifiers, orders, customer records       | yes  | optional |
| Toast                    | Items, modifiers, orders, customer records       | yes  | optional |
| BakeSmart / Cybake / FlexiBake | Production sheet, decorator calendar       | yes  | optional |
| Google Calendar          | Decorator hours, tasting bookings                | yes  | yes   |
| Twilio (or similar)      | Outbound SMS for confirmations and reminders     | no   | yes   |
| Email provider           | Outbound email (SendGrid, Postmark)              | no   | yes   |
| Slack                    | Owner alerts for cottage-food and price flags    | no   | yes   |
| OpenClaw Memory          | Cross-run state for orders, capacity, accounts   | yes  | yes   |
| OpenClaw Heartbeat       | Scheduled intake review and wholesale cutoff     | yes  | yes   |

Write-backs to the POS or bakery management system are optional. Most
bakeries start read-only and have the owner commit any system changes
manually. After two weeks of validation, flip write on for low-risk fields
like order tags, internal notes, and standing-order quantity adjustments.

## Compliance notes

The skill ships with a 50-state cottage-food rule matrix as a starting point.
This is not legal advice. The owner is responsible for the final jurisdiction
call on any interstate or unusual-route order. The skill's job is to surface
the conflict before the order is accepted, not to make the legal call.

For wholesale accounts, the skill respects each account's purchase-order
process. It will not draft a price exception or a SKU substitution without
explicit owner approval.

## Configuration

```yaml
config:
  bakery_name: "Your Bakery"
  home_state: "CA"
  decorator_count: 2
  weekly_decorator_capacity_hours: 64
  lead_time_minimums:
    smash: 72h
    birthday_simple: 48h
    birthday_themed: 5d
    tiered_2: 5d
    tiered_3: 7d
    sculpted_character: 10d
    wedding: 4w
    wedding_with_sugar_flowers: 8w
    cupcake_tower: 5d
  approval_mode: owner_approves_all     # or "autonomous_after_2_weeks"
  autonomous_template_allowlist:
    - custom_order_within_lead_time
    - wholesale_daily_confirmation
  wholesale_accounts:
    - account_id: hilton_downtown
      route: downtown
      cutoff_time: "17:00"
    - account_id: blue_bottle_lakeshore
      route: east
      cutoff_time: "17:00"
  tasting_followup_cadence: [7d, 21d, 60d]
  cottage_food_matrix_last_reviewed: "2026-04-01"
```

## Quick install

```bash
mkdir -p ~/.claude/skills
mv bakeries.md ~/.claude/skills/bakery-custom-order-and-wholesale.md
# Edit the config block to match your bakery
```

Launch OpenClaw and the skill is live. Trigger it manually with
`run morning custom-order review` or `compile decorator forecast` or wait
for Heartbeat to fire on the configured schedule.

## Want it wired to your stack?

This SKILL.md is the starting point. If you want it plugged into your
specific POS, decorator calendar, wholesale book, and brand voice on a
fixed-price two-week clock, with the founder writing every line, the door
is at https://www.adhirajhangal.com/work

Install in 60 seconds

1. 1

   Drop the file into your OpenClaw skills directory

   Save the downloaded bakeries.md as ~/.claude/skills/bakery-custom-order-and-wholesale.md (or your project-level .claude/skills/). OpenClaw picks up new skill files on next agent launch, no restart command required.

2. 2

   Connect your POS or bakery management system

   Edit the integrations block to point at your Square for Retail, Toast, BakeSmart, Cybake, or FlexiBake export. Read-only is enough to start. The skill includes prompts that translate your daily items, modifiers, and decorator calendar into the agent's working memory.

3. 3

   Launch in approval mode, then flip the easy templates to autonomous

   Start with the owner approving every custom-cake reply, wholesale confirmation, and lead-time pushback for the first two weeks. The skill's defaults route anything that touches a deposit, a wedding tasting, or a wholesale price exception to a human. After two weeks, flip the standard lead-time replies and the wholesale-standing-order confirmations to autonomous.

Example conversation

Common questions

Related free skills