Skip to main content
Intempt
Coming soon

Fulfillment, returns and refunds

Answers whether orders are shipping on time and where return spikes occur by tracking fulfillment rates, returns, and refunds by product.

Authored by Intempt Technologies

Recipe curators

Agentic workflow

Coming soon

1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Build the operations board

    Coming soon

    Blu builds a step

About this recipe

When to use it

Order flow, returns, and quality issues by product usually surface separately, after the customer's already unhappy. This puts the operational picture in one place for the ops team.

What it delivers

Tracks order flow, fulfillment rate, returns, refunds, and quality issues by product for the ops / fulfillment view.

How you prompt this

Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.

Tell Blu Agent what you want

“Answers whether orders are shipping on time and where return spikes occur by tracking fulfillment rates, returns, and refunds by product.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.

Outputs

    How the recipe runs

    Blu follows the steps in order and shows you each one before anything goes live.

    1. 01Build the operations boardCreate a Dash board (12-column composition canvas) titled "E-commerce Operations". Persona: Operations Lead, Fulfillment Manager, or Customer Service Lead. Question answered: "Is the post-purchase machine working? Where are quality issues hiding?" Distinct from the E-commerce Revenue Dashboard: Revenue is "are we selling" (top of order); Operations is "are we delivering" (bottom of order through return). Zero card overlap. Board-level configuration: - defaultDateRange: last_30_days - exclusionPeriod: today (operations data lags by hours) - visibility: project - boardFilters: none by default - boardBreakdowns: product_category (derived from items): pushed down to applicable cards Layout: 4 rows. Row 1: Operational KPIs (heightPx: 200, four metric cards at widthUnits: 3): - Card 1: Insights metric to source recipe: order-status-flow, vizType: metric, titleOverride: "Orders (30d)" - Card 2: Insights metric to source recipe: order-status-flow, vizType: metric, titleOverride: "Fulfillment Rate" - Card 3: Insights metric to source recipe: return-rate-by-category, vizType: metric, titleOverride: "Return Rate (30d)" - Card 4: Insights metric to source recipe: refund-rate-by-product-and-category, vizType: metric, titleOverride: "Refund Rate (30d)" Row 2: Order flow (heightPx: 400, two cards at widthUnits: 6): - Card 1: Insights to source recipe: order-status-flow, displayMode: chart, vizType: stacked_column (created/fulfilled/refunded/cancelled distribution over time) - Card 2: Insights to source recipe: time-to-ship-distribution, displayMode: chart, vizType: bar (histogram with cumulative line) Row 3: Quality issues (heightPx: 440, two cards at widthUnits: 6): - Card 1: Insights to source recipe: return-rate-by-category, displayMode: chart, vizType: bar - Card 2: Insights to source recipe: refund-rate-by-product-and-category, displayMode: chart, vizType: bar Row 4: Pre-purchase friction and support (heightPx: 400, two cards at widthUnits: 6): - Card 1: Funnel to source recipe: checkout-form-friction, displayMode: chart, vizType: funnel_steps (per-checkout-step friction) - Card 2: Path to source recipe: support-deflection-paths, displayMode: chart (paths preceding Ticket created: operational quality intelligence) Annotations: - Row 1 Card 2 ("Fulfillment Rate") is the operational headline. <90% indicates a backlog or capacity issue. - Row 2 surfaces the operational tempo (Card 1: order flow over time) and ship-time distribution (Card 2: how fast are we actually shipping). The histogram is more useful than just "average ship time" because it surfaces the long tail. - Row 3 surfaces post-purchase quality (categories with high return AND high refund rates are the inventory-quality problem children); Row 4 surfaces pre-purchase friction and support load. Taxonomy notes: - All source recipes are taxonomy-grounded. order-status-flow and time-to-ship-distribution are new v5 recipes designed specifically for this dashboard's operational use case (replacing earlier inline custom specs). - Placed order, Order fulfilled, Order refunded, Order cancelled are all canonical events. - Time-to-ship is computed from (Order fulfilled.Created date − Placed order.Created date) joined on order_id.

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /ecommerce-operations-dashboard in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Intempt TechnologiesDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Intempt TechnologiesPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Intempt TechnologiesReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Intempt Technologies

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Product swap in a sceneReplaces the product in a shot you already have with a different one, keeping the scene, lighting and shadow the same.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe