The Supply Chain KPI Dashboard Every Bangladesh RMG Factory Needs: Order Intake, Material Receipt and On-Time Delivery (Part 1)

A supply chain dashboard should link each order to stock and shipment dates. Track key performance indicators, or KPIs, to find late orders and missing goods. Use these records with the operations dashboard in Part 2 to check whether the factory can keep its next promise.

Start with the decisions the team must make

A merchandiser needs to know which missing material threatens the next production step. A sales head needs to know which confirmed bookings explain the gap against plan. A planner needs to know whether a proposed date fits the resources already committed. These questions need linked views, but they do not need identical screens.

A dashboard should make exceptions visible while there is still time to respond. The team might expedite a zipper or seek an approved substitute. It might change a release sequence or discuss a new shipment date with the buyer. The data do not choose the response by themselves. Cost, quality, available capacity and the buyer's agreement still matter.

For each measure, define its event, scope, denominator, cutoff and owner. What does a tile labelled material complete mean? The material may be ordered, received or released. State which event it records. A green delivery percentage is equally weak if overdue open orders disappear from its denominator. Clear definitions help the morning meeting. They also let the team explain the figures in a buyer review.

Start with three connected questions. Are confirmed orders meeting the business plan? Will usable material be available when the route needs it? Did the factory meet its agreed shipment promise? Add detail when it changes a decision, rather than filling every available space with another chart.

Measure order intake in value and work content

The sales target starts with expected demand. It also reflects the buyers, product mix and prices. Translate that view into a fiscal-year value plan and a monthly plan by sales owner. Keep the underlying assumptions so a change in product mix can be explained. The same value can represent very different amounts of factory work.

For example, a month with more complex garments may reach its value target with fewer pieces. It may still consume more sewing hours than the previous mix. Another month may book many simple pieces at a lower value per piece. A value chart alone cannot tell the planner which month is harder to deliver.

Standard allowed hours, or SAH, express the order's standard work content. If SMV is measured in minutes per garment, the relationship is:

Order SAH = order quantity × garment SMV ÷ 60

An illustrative order of 12,000 garments at 18 SMV requires 12,000 × 18 ÷ 60 = 3,600 SAH. A second order of 8,000 garments at 24 SMV requires 3,200 SAH. Together they represent 20,000 garments and 6,800 SAH. The garment count and work content should both remain visible.

SAH is a load measure, not elapsed production time. To complete 3,600 SAH, the factory needs suitable staff and skills. Working time, efficiency, materials and the route also affect the finish date. The SMV guide explains why the standard must describe a defined method and allowance basis. Changing the standard changes the apparent load. Keep the version used for booking.

Use the target that belongs to the reporting date

Suppose the full monthly value target is $1 million. The approved month-to-date target is $600,000. Confirmed net bookings at the cutoff are $552,000. Achievement against the elapsed-period plan is $552,000 ÷ $600,000 × 100 = 92%. The gap is $48,000, or 8% below that plan.

Comparing the same bookings with the full-month target gives 55.2%. That number can be useful as progress toward month-end, but it answers another question. Label both measures if the team needs both. Otherwise an ordinary mid-month position may look like a failed month.

Confirmed intake should reflect approved changes and cancellations. Keep enquiries and tentative bookings in a separate forecast view. State the currency and exchange-rate rule. A booking may change after the cutoff. Show that later change and preserve the previous report. This preserves a fair record of what was known at each review.

Track material at the level where shortages occur

An order can have most of its materials in the factory and still be unable to start. A small quantity of buyer-specific labels may block packing. One shade group may have enough fabric in total but too little for a planned lay. Show each material line, its date and whether it is suitable. A percentage of completed purchase orders cannot show every shortage.

Use the purchase-order line and its due schedule as the basic procurement record. Distinguish the supplier's original promise, approved changes and the current expected date. Capture gate arrival and receipt posting. Keep quality release separate when it occurs later. A truck at the gate is not the same as usable stock at the work centre.

The supplier lead-time guide follows the same distinction. For an order promise, the useful comparison is expected usable date against material need date. Show the short quantity, the affected jobs and the latest time at which a recovery action can still help.

Consider an illustrative zipper requirement of 12,000 pieces. The factory has received 10,000, but 1,000 are on hold. Only 9,000 are released for use. The usable shortfall is 12,000 − 9,000 = 3,000 pieces. A physical-receipt view would show a smaller 2,000-piece gap and conceal the hold.

A later delivery of 2,000 does not solve the whole problem unless the held 1,000 also become usable. The alert should show both causes. Procurement can pursue the undelivered quantity while quality resolves the held quantity. One broad label such as supplier late would obscure that division of work.

Protect the meaning of a material readiness percentage

Define what counts as ready. A line-count measure might report nine of ten required material lines as ready. A quantity-weighted measure might look better or worse. Neither proves that the order can start if the missing line is essential. Pair a summary percentage with a list of blocking requirements.

Material criticality deserves its own field. The ABC-XYZ inventory guide can help set review effort, but annual value is not the same as production risk. A cheap custom label may be urgent. A costly common material may have several approved substitutes.

Apply stock policies only where the demand and reuse pattern justify them. EOQ and periodic review can support repeat trims. A style-specific print may need an order-based purchase plan. Show the chosen policy and the actual commitment. Leftover stock is not always useful safety stock.

Define on-time delivery before calculating it

On-time delivery, or OTD, can refer to several events. It may mean factory shipment, carrier handover or arrival at the buyer. This article uses the factory's agreed shipment event. A buyer contract may define another event. Use that event in the buyer's scorecard and label it clearly.

A common shipment-cohort calculation is:

Shipment OTD = orders shipped on time ÷ all orders shipped in the period × 100

Define what counts as one order and how split shipments are handled. If an order is due in full, an early partial shipment may not satisfy the commitment. Preserve the original promise date and record approved revisions. Moving the due date just before shipment can make a weak process look reliable.

Suppose 50 orders shipped this month and 47 met the chosen promise date. Shipment-cohort OTD is 47 ÷ 50 × 100 = 94%. This describes the shipped orders. It says nothing about orders that are already overdue but have not yet left the factory.

A due-date-cohort measure uses all orders due in the period. Assume 55 orders were due, 47 shipped on time, three shipped late and five remain late and open. Due-date-cohort OTD is 47 ÷ 55 × 100 = 85.45%. Both calculations are valid for their stated populations. Combining them without explanation would mislead the reader.

Show the late work beside the percentage

At minimum, display overdue open orders, overdue quantity and days late beside shipment OTD. Add the next required action for each major exception. A rate should lead to the work behind it, rather than ending the discussion with a colour.

Two factories can both report 94% while facing different problems. One may have three small orders delayed by a day. Another may have one major order delayed by two weeks. Value, quantity and severity views help explain the difference. They should supplement the order-count rate, not quietly replace its denominator.

Show the trend with its counts. A rate may fall from 94% to 90%. Was that based on ten orders or a thousand? Show the counts. Check changes in order mix and promise rules before judging the trend. A mid-90s target may be a local business goal; it is not a universal definition of excellent performance.

Build a small set of linked views

The dashboard can be several focused screens using the same order keys. Daily views handle exceptions. Weekly views support planning and supplier review. Monthly views support commercial performance and closeout. Update frequency should follow the decision, not the desire to label every number real time.

A user should be able to move from a red material alert to its purchase line, receipt and release record. The buyer scorecard should use the same shipment events as the order view. A shared model lets one event support several decisions. Staff do not have to enter it again for each chart.

Keep buyer and supplier scorecards fair

A supplier delivery score needs its own event definition. A truck reaching the gate by the promised date does not establish that the full purchase line was available for use. Show physical receipt, quantity completion and quality release as separate events. A partial receipt may be acceptable. Keep its agreed quantity and date, so the team can assess each split delivery on its own terms.

The buyer scorecard also needs context. A late approved specification can delay an order. A missed factory milestone can do the same, but each cause may need a different response. Keep the original commitment, the accepted revision and the actual result. These records allow a fair discussion without silently rewriting history. Use the revised promise to plan recovery. Keep the original promise to assess how reliably the factory met its commitment.

Avoid combining delivery, quality and payment into a single unexplained score. A small quality failure may have a very different consequence from a short delay. Show each measure with its counts and period. Explain any weighting used in the management summary. The underlying evidence should remain accessible when the overall score looks healthy.

Reconcile inventory through the full order life

A booking is not a receipt, and a receipt is not always released stock. An issue to production is not always final consumption. Returns, transfers, scrap and adjustments can all affect the balance. The closeout view must show these movements on a common unit and location basis.

Start the stock balance with opening stock. Add receipts and transfers in. Deduct issues, supplier returns, transfers out and recorded scrap. Then apply any authorised corrections. Production returns increase the relevant store balance when they physically return. The exact ledger design may differ, but each movement should be counted once.

For example, a store starts with 500 m allocated to an order, receives 5,800 m and issues 5,600 m. Production returns 180 m, and the store sends 100 m back to the supplier. With no other moves, closing stock is 500 + 5,800 − 5,600 + 180 − 100 = 780 m. Whether all 780 m remain usable is a separate quality question.

Give leftover stock an owner without assuming it is a loss

Some factories call the closeout view merchandiser liability. Use the term carefully. It can identify who must resolve a style's leftover stock and open commitments. It does not establish a personal debt, and it does not prove that all remaining stock has no value.

Check whether another approved order can use the fabric or buyer-branded trims. Review which supplier commitments can be cancelled. Finance should assess the stock's value and likely recovery. It should use the applicable accounting rules for any write-down or claim. The dashboard supplies quantities that can be traced. Displaying a balance does not settle its value.

A roll reserved for another style remains the same physical roll. Reallocation changes its intended use, not the amount in the store. Use common stock keys. Adding style reservations as if each were separate physical stock can double the reported balance.

Make Central Planning test the promise

Central Planning connects the commercial request with materials, people and equipment. Before a date is confirmed, it checks the order's route, work content, readiness and existing commitments. Start with the monthly plant total. Then check each needed machine and skill group for a shortage.

Microsoft's finite-capacity planning documentation describes scheduling that considers resource limits and existing reservations. The principle is relevant beyond that product. The proposed work must fit the resources actually available in the required periods. A software result remains dependent on the constraints and calendars entered.

An experienced planner may already use a line-loading sheet and backward schedule. Their knowledge of styles also matters. Preserve that knowledge by recording the assumptions. A blank cell on the loading sheet is a possible opening, not proof of spare capacity. Add quantity, SMV, staffing, learning expectations and the effect on later stages.

Backward planning starts at the shipment date and works toward the required material date. Include packing, finishing, sewing, cutting, transfers and approvals as applicable. Then check whether the required resources are available on those dates. A sequence of backward dates does not, by itself, resolve competing orders.

Calculate effective capacity on the same basis as load

For a simple labour-based estimate:

Available SAH = available operators × working minutes per day × working days × expected efficiency ÷ 60

Take 80 operators working 480 available minutes per day for 22 days. Assume expected efficiency of 65%. Planned labour time is 80 × 480 × 22 ÷ 60 = 14,080 hours. Expected standard-hour output is 14,080 × 0.65 = 9,152 SAH. These are illustrative assumptions that need support from comparable work.

If firm load is 7,200 SAH, the apparent balance is 1,952 SAH. Suppose the factory also chooses a separate 10% reserve of effective capacity for uncertainty. That reserve is 915.2 SAH, leaving 1,036.8 SAH for further booking on this broad basis. The reserve is a local example, not an industry requirement.

Do not subtract the same loss twice. Expected efficiency may already reflect ordinary delays. Allowing for those delays again would understate capacity. State the purpose of the reserve. It might cover uncertainty beyond the expected operating level. Likewise, do not multiply a standard-hour load by efficiency again when comparing it with effective SAH.

Skill and route constraints still need their own checks. Spare standard hours in one department cannot automatically replace a shortage in another. Inspect the work centres that govern the order's finish date before sales treats the broad balance as an available promise.

Control forecasts and changes through planning zones

A frozen zone protects near-term commitments. It need not mean that an emergency can never be handled. It means that a change requires a visible impact review and the right approval. A slushy zone allows defined changes after checking their effect. A forecast zone reserves capacity for business that is not yet firm.

Set the zone boundaries from the factory's lead times and decision needs. No fixed number of weeks suits every plant. A long fabric commitment and a short finishing task may need different controls. Publish which fields can change and who decides when another order would be displaced.

Forecast reservations need expiry dates. When an order confirms, match it to the earlier reservation and convert or release that reservation. Otherwise the same expected work can be counted once as forecast and again as firm load. Check quantity, SMV and route again if confirmation differs from the forecast.

A priority rule should also explain its exceptions. Confirmed work may normally rank ahead of forecasts, while due dates and buyer commitments guide the ready queue. Material readiness and bottleneck use still matter. Show what moves later when one order is advanced. A local override can be reasonable, but its effect should not remain hidden in a phone call.

Work through a style-change request

Return to the 12,000-piece order at 18 SMV. Its load is 3,600 SAH. A proposed style requires 18% more standard time at the same quantity. Its SMV becomes 18 × 1.18 = 21.24, and its load becomes 4,248 SAH. The change adds 648 SAH.

Suppose the broad planning balance has 1,036.8 SAH available for booking. The added load appears to fit, leaving 388.8 SAH. That does not settle the request. The extra work may need a scarce operation. Its required period may already be full. The new style may also need different fabric approval, attachments or finishing time.

Run the affected route and identify the orders whose starts or finishes move. If a detailed schedule shows a four-day delay, retain that schedule as evidence. The four days cannot be derived from the 18% change alone. Discuss the actual options: a revised date, a split quantity, another approved resource or the original style.

Design the data so a total can be traced

The order key should connect booking, material requirement, production and shipment. Keep separate identifiers for purchase lines, receipt events and shipment lines. An order can have several receipts and several shipments. Joining those detail tables without respecting their different levels can multiply quantities.

Suppose one order has two receipts and three shipment records. A careless join can produce six rows, each with the same order value. Summing those rows reports six times the true value. Aggregate at the required level or use a sound reporting model before calculating the measure.

Microsoft's guidance on star-schema models explains how to structure descriptive data and event measures. The practical requirement here is simpler: every count and sum must have a known row meaning. Reconcile the result with the source ledger before users rely on the chart.

Show event time and refresh time separately. The receipt may have occurred at 10:00 and been posted at 14:00. The report may refresh at 14:15. Those timestamps explain whether a late alert reflects a late event, late capture or late reporting. A failed update should be visible, not presented as fresh data.

Use Bangladesh trade context with dated sources

The following source check is dated 22 October 2026. BGMEA's export table lists RMG exports of $38.70115 billion for fiscal 2025–26 and $39.34697 billion for fiscal 2024–25. The change is approximately −1.64%. These are fiscal-year export values, not a direct measure of individual factory demand or foreign market share.

Keep fiscal and calendar periods separate. An export value by destination is not Bangladesh's share of that destination's total imports. For the US import-side view, OTEXA's official reports provide defined product and time series. Match the product coverage, period and currency before making comparisons. A national change cannot by itself explain one buyer's sourcing decision.

Bangladesh is due to leave the UN’s least developed country group on 24 November 2029. The UN’s status page records the new date. The old plan used 24 November 2026. Check the latest UN decision before using a date in a quote or plan.

The EU Council's May 2026 adoption notice states that the revised GSP framework applies from 1 January 2027. Its arrangements and the adopted text distinguish eligibility, product treatment and safeguards. Graduation status does not establish the duty on every garment on the same day.

For a quotation, record the tariff code, origin basis, import date and applicable preference. A hypothetical 20% reduction from a 12% rate produces 9.6%, not a reduction of 20 percentage points. That arithmetic is not a tariff determination for a Bangladesh product. Keep scenarios separate from verified rates. The dashboard can track the assumption and its review date. The commercial or customs specialist should check which rule applies.

Digitise the next decision that is failing

A factory does not need a separate application for every department. Shared ERP records and a reporting layer may serve several users. A controlled spreadsheet can support an early pilot. Define its keys and versions, and name who maintains each record. The apparel ERP checklist turns system requirements into observable tests.

Choose the first pilot from an actual failure. If sewing keeps discovering material holds too late, start with receipt and quality release. Connect those events in the first dashboard. If bookings exceed feasible capacity, start with order SAH and the loading calendar. If leftover material is poorly explained, start with movements and style closeout.

Test the pilot with real transactions, including a partial receipt, a held lot, a split shipment and a cancelled order. These cases test the process under strain. Agree who responds to each alert. Define what evidence closes it.

Run the meeting from exceptions to decisions

A daily review can start with orders whose next material or production milestone is at risk. For each one, ask what changed, what quantity is affected, which date is threatened and who can act. Record the chosen action and its next check. The aim is to leave with decisions, not merely a list of red cells.

A weekly review can compare intake, capacity and supplier trends. Review forecast reservations that are nearing expiry. Examine recurring reasons for late usable receipt. Check whether the planned efficiency still represents the styles in the next load. Use the floor evidence from Part 2 to revise future assumptions rather than quietly moving past dates.

At month-end, reconcile shipment cohorts and inventory closeout. Keep late open orders visible until their final outcome is known. Review whether recovery actions solved the problem or transferred cost elsewhere. An expensive expedite may have protected a shipment. It may have been justified. Keep its cost in the order's record.

The dashboard design guide provides further principles for making these views easy to read. A useful dashboard lets the team answer a question quickly and then inspect the evidence. More charts do not compensate for an unclear event definition.

Questions factories often ask

Can this work without a full ERP implementation

Yes, if the records share clear keys and the team controls changes, cutoffs and reconciliation. A maintained line-loading sheet can be useful. The burden rises as orders and revisions multiply. Introduce software where it can solve a known problem in sharing work. Keep the definitions and checks that make the records reliable.

Should order intake be measured in pieces or money

Both can be useful, but neither replaces standard work content. Use value for commercial performance, pieces for physical quantities and SAH for the standard labour load. Explain the product mix that links them. A factory can meet a value target and still overload the work centre needed by that mix.

Is a high OTD rate enough to judge delivery performance

No. State the shipment event and cohort, show counts and overdue open work, and inspect delay severity. Add quantity or value views when they help the buyer discussion. A rate without its underlying orders can hide late unfinished work or be distorted by changes in what counts as an order.

Where should Central Planning draw the frozen zone

Use the point at which changes become costly or disruptive for the relevant route. Material commitments, style setup and buyer approvals may set different limits. Publish the local rule and allow controlled exceptions. The word frozen should make the impact review clear, rather than prevent a necessary response to a genuine change.

A credible supply chain dashboard makes the delivery promise traceable. It connects the booking to usable material, feasible capacity and the shipment event. When the assumptions change, the affected work becomes visible and the next decision has an owner. That shared record is the foundation for a useful conversation with the buyer.

See also the buyer’s journey in Bangladesh (Part 2).

Correction, 4 November 2026: We updated the UN date for Bangladesh to leave the least developed country group.

References and further reading

• BGMEA — Export performance tables.

• US International Trade Administration — OTEXA import data.

• United Nations — Bangladesh LDC country profile.

• United Nations — Bangladesh graduation status.

• Council of the EU — Revised GSP adoption notice.

• Council of the EU — Adopted GSP text.

• Microsoft — Finite capacity planning and scheduling.

• Microsoft — Star-schema guidance for reporting models.