News: Meet Avesta Labs at the Bengaluru Tech Summit, 17–19 November, Stall H1A036 at BIEC. See event details

BBF Packaging

Case study · Packaging manufacturing · India

How BBF Packaging clears delayed sales orders faster with an AI agent

BBF Packaging's team chased late sales orders by hand every Friday, and lost last week's answers by the next. Our agent gets a reason for every order from Production, sends it to the team that has to act, and remembers every decision. Orders no longer sit unchanged for weeks.

The problem
Comments and decisions were lost every week, so the same questions came back.
What we built
An agent that gets a reason for every late order, routes it and keeps its history.
Business outcome
Lower sales order age. Delayed orders clear faster.
Status
Live for about three months.
Book an AI Kickoff

The same problem shows up in

  • Packaging and printing manufacturers
  • Make-to-order factories on SAP
  • Any business that chases late orders by email

If the reason an order is late lives in an inbox, you will ask again next week.

Before and after.

Before

The same chase, every Friday

A weekly routine run by hand, with nothing carried over.

  1. 1Download the delayed order report from SAP
  2. 2Email each salesperson and ask why orders are late
  3. 3Collect and analyse the replies
  4. 4Take serious cases to management, then repeat next Friday

Last week's decisions were lost in email, and some weeks the analysis wasn't done at all.

After

Every order keeps its story

Still a Friday routine. The chasing and sorting are the agent's.

  1. 1The team uploads the SAP report to the agent
  2. 2Production get an email, and one button opens their queue
  3. 3They pick a reason for each order
  4. 4The agent sends it to the team that has to act

No longer done by hand

  • Emailing for comments by hand
  • Reading and sorting every reply
  • Digging through old emails

~120

Delayed sales orders

In the weekly report.

5

Salespeople

Asked only when Sales is needed.

0

Emails written by hand

The agent does the chasing.

5

Teams an order can reach

Production, Purchase, Sales, SAP, Management.

The problem

Why the chase kept failing.

Every week started from zero

Last week's comments and decisions weren't kept anywhere searchable.

Answers lived in email

Finding one order's decision meant digging through old threads.

The analysis took the time

Reading every reply and deciding who should act was slow, so it wasn't done properly every week.

Management saw it late

The team had to spot the orders that needed management by hand.

Why not just a better report?

SAP knows which orders are late. It doesn't know why.

So we kept SAP as the source and put the agent on the other side of the report.

  1. 01

    A report shows late, not why

    The reason sits with the people who know the order.

  2. 02

    Comments are in people's own words

    “Board received late, dispatching on the 28th.” A column can't read that. An agent can.

  3. 03

    A report forgets

    Next week's report doesn't know what was said this week. The agent does.

What they asked for

Stop repeating the Friday chase, and never lose what anyone said about an order.

One more: send each order to the team that can move it, and bring in management only when the rules say so.

So the goal was to clear delayed orders faster, not to send more emails.

The agent

What it does.

Starts from the SAP report

The team uploads the delayed order report. The agent loads every line.

Production comments first

They know why an order is late. An email button opens their queue, and they pick a reason and save.

Reads the comment

It works out what the comment says about the delay.

Routes by the comment

To Purchase, Sales, SAP or management. Sales and Purchase clarify as a second step.

Remembers every week

Every comment and decision stays with the order, so you can see why it was late.

A dashboard on request

Orders by team, the oldest orders, critical reasons and orders with no action.

What it deliberately does not do
It never connects to SAP, never invents a dispatch date, and never adds management just because an order is old.

The comment queue

What Production sees.

SO Comment Queue

Week of 23 Oct · 4 visible

Needs comment: 4

Select a reason, fill any required fields and save.

View:AllNeeds comment only
OrderItemAgeBalanceComment for this week
SO-B201FG-1042112 d5,700
Select a reason…Save

SALES04 SepWaiting for dispatch clearanceShow history (6)

SO-B207FG-105864 d1,800
Select a reason…Save

PROD16 OctDispatching on 30 OctShow history (3)

SO-B214FG-107738 d3,000
Select a reason…Save
A recreation. Every order, number and date in it is constructed.

Production pick from a short list of reasons, or write their own. Earlier comments sit under each order. Sales and Purchase see the same queue when the agent needs their clarification.

The dashboard

What management sees.

SO Analysis Report — Management Dashboard

XLSX export

Team records

Management can comment on any order.

  • Production (12)
  • Purchase (6)
  • Sales (2)
  • SAP (1)
  • Management (5)
OrderAgeTeamReasonStatus
SO-A10192 dProduction + ManagementPromised date passed, not dispatched.Escalated
SO-A10557 dProduction + ManagementCause changed from material to QC hold.Moving target
SO-A10366 dPurchaseMaterial due beyond 20 days.Open
SO-A10241 dProductionDispatch promised within 15 days.Promise pending
SO-A10435 dSalesNo dispatch clearance.Open
SO-A10648 dSAPDispatched, but still open.Check SAP
A recreation. Every order, number and date in it is constructed.

Each order sits under the team that has to act. Management sees what is oldest, what is critical and what has no action.

One order, three Fridays

How an order's story builds up.

  1. Week 1 · SO-A105

    Production said

    “No board. Expected on 12 Nov.”

    Purchase

    Material pending.

  2. Week 2 · SO-A105

    Production said

    “Board received late. Dispatching on 28 Nov.”

    Production + Purchase

    Date logged as a promise.

  3. Week 3 · SO-A105

    Production said

    “Order is on a QC hold.”

    Production + Management

    New cause, and the promised date passed. Management is added.

A recreation. The order and its comments are constructed.

Without last week's comments, week 3 looks new. With them, the agent sees a reason that keeps moving.

Trust and data

Safe to run.

An agent that routes orders can send one to the wrong team if it's careless. So it follows written rules, one order at a time.

No SAP access needed

It works from the uploaded report and can't change anything in SAP.

Only what was said

A dispatch date comes from this week's comment, never an estimate.

One order at a time

A comment on one order can't change where another goes.

Management by rule

Added only through set triggers, never for age alone.

The process

How we worked.

  1. 01First

    Their judgement became the rules

    Each kind of delay, who owns it and when management steps in, written down as the agent's instructions.

  2. 02Build

    One order at a time

    The agent analyses one order line per run, so one odd comment can't affect another.

  3. 03Connection

    An upload, not an API

    SAP's API wasn't opened up, so the team uploads the report. The agent starts from there.

  4. 04Live

    In use every Friday

    BBF's team has used it for about three months.

The hard part

Judging a reason the same way, every week.

The obvious build: a model that reads each comment and decides who should act, with nothing written down.

Why that fails

One sentence can point three ways

“Awaiting clearance” is Sales. “Board received late” is Production and Purchase. “Will update” needs management. A model left to decide would drift, and no one could say why.

What we did instead

Rules first, in strict order

Each kind of delay has a written rule, checked in priority order. Every result says which rule fired and why.

The Friday routine didThe agent does
Judged each reply by handChecks the comment against the rules, in order
Remembered what it could from last weekCompares with every earlier comment, and flags a shifting reason
Took a date on trustLogs a date only if stated, and escalates it if it passes

Where it is better than before

Memory

Every decision stays with the order.

Consistency

The same comment gets the same routing.

Time

Upload a report instead of writing emails.

Visibility

The dashboard is there any day, not just Friday.

How we held that bar

Every result names the rule that fired, so anyone can check it against what Production said.

Faster is easy. The hard part is never sending an order to the wrong team.

Six months from now

How it stays predictable.

The agent's instructions are written, not improvised. For every order it asks the same questions in the same order.

  1. 1Does the comment end the check, like a clearance hold or an already dispatched order?
  2. 2Is a stated dispatch date within 15 days, past, or missing?
  3. 3Has the reason shifted, or does a trigger allow management?
  4. Goes live

An example from the rules

“Awaiting clearance” on a 600-day-old order still goes to Sales. Age alone never sends it to management.

Find out what your Friday chase is costing you.

A short discovery session about the report your team chases every week. We'll show you what an agent would do with it.

Book an AI Kickoff

Or email hello@avestalabs.ai