How to operationalize circular RTM for reliable field execution across distributors and outlets

Expiry risk, retail returns, and packaging waste should be treated as core RTM metrics because they directly consume gross margin, distort demand signals, and increase cost-to-serve just as tangibly as low fill rate or poor numeric distribution. In fragmented traditional trade, unmanaged write-offs and waste can silently erode profitability even when top-line volume looks healthy.

From a P&L perspective, expiry write-offs hit cost of goods sold, while frequent returns drive extra freight, handling, and sorting costs; both also inflate effective trade-spend when schemes are used to clear aged stock. Packaging waste—especially under EPR-type regimes—can translate into compliance fees, penalties, or higher future collection obligations, which become recurring operating costs. When RTM systems surface expiry exposure by SKU and territory, manufacturers often find mid-single to low-double-digit percentages of secondary sales at risk in some categories.

The justification for elevating these to core RTM metrics usually comes from quantified improvements: modest reductions in expiry and returns (for example, cutting write-offs by a few percentage points of sales in sensitive categories) can deliver margin uplift comparable to major price increases, without channel conflict. In addition, better control of returns and waste reduces audit risk and strengthens ESG narratives, which increasingly influence access to capital and retailer partnerships.

Modern RTM platforms capture expiry dates, batch data, and stock ageing at distributor and outlet level by extending standard stock and sales transactions with mandatory batch- and date-level attributes, then reconciling movements across DMS and SFA. Reliability for finance and audit comes from consistent master data, standardized capture points, and cross-checkable flows.

At distributor warehouses, batch and expiry are typically recorded at goods receipt (primary invoice or GRN) and carried through to secondary invoices. Each stock line in the DMS includes SKU, batch number, manufacturing or expiry date, quantity, and sometimes storage conditions. When sales reps place orders via SFA, the system either pulls available batches from the distributor DMS in real time or uses allocation rules so that near-expiry stock is prioritized, ensuring that batch-level decrements match invoice records.

For outlets, expiry data may be captured via photo audits, scan-based checks, or manual entry during store visits, especially for high-risk SKUs. The expiry risk dashboard then aggregates stock positions, days-to-expiry buckets, and historical sell-out velocity to estimate likely write-offs. Audit confidence increases when the RTM system stores immutable event logs (who updated which batch, when), aligns batch IDs with ERP and tax documents, and provides reconciliation views that tie opening stock, receipts, issues, returns, and destructions back to financial postings.

To consistently record returns, damages, and packaging recovery without slowing execution, RTM teams need to standardize a few simple workflows and embed them into tools field users already rely on for orders and collections. The change is less about adding new apps and more about making reverse events as easy to capture as a sale.

For distributors, this typically means configuring clear transaction types in DMS—returns from retailer, damage write-off, packaging return—and training staff to book them at the moment of physical movement rather than in end-of-day batches. Automated prompts tied to credit-note creation, claim submission, or stock adjustments help maintain discipline. For sales reps, SFA workflows add one or two quick steps on the visit screen: a structured reason code for returns (expiry, damage, wrong supply) and count of units or packaging items collected, ideally supported by barcode scanning or quick lists for common packs.

Behaviorally, adoption improves when these actions are linked to existing KPIs and incentives, not treated as extra reporting. For example, route compliance dashboards can show “returns recorded vs. collected value,” and gamified scores can reward high-quality data capture. Managers must also reassure field teams that accurate reporting of damage and waste will not automatically penalize them for issues outside their control, otherwise reps will avoid logging problems and the system will under-report reality.

Sustainability-oriented KPIs can be integrated into existing RTM control towers by treating them as additional dimensions on familiar sales and distribution views, rather than as a separate ESG dashboard with dozens of new numbers. The goal is to surface expiry and waste risks where sales managers already look for volume and coverage issues.

Practically, expiry write-off rate might appear as a small panel next to gross sales and contribution, with color-coded thresholds and drill-down by region, channel, or key account. Reverse-logistics recovery rate and packaging waste per case can be overlaid on territory maps and route performance tables that users already use, using traffic-light indicators or simple trend lines rather than complex charts. Filters let users toggle between “sales-only” and “sales + sustainability” views without overwhelming first-time users.

Control-tower design should prioritize a handful of composite indicators—such as an “RTM health score” that includes expiry and recovery components—while allowing expert users to drill into more detailed sustainability metrics. This layered approach keeps dashboards actionable for frontline managers, while still providing enough depth for ESG and operations specialists to analyze root causes and plan interventions.

Finance leaders can quantify ROI on expiry tracking and reverse logistics by comparing baseline write-offs, returns costs, and compliance exposures with post-implementation performance, and by attributing improvements to specific RTM capabilities. The analysis typically combines direct P&L gains with risk and working-capital benefits.

Direct ROI measurement usually tracks reductions in: (1) expiry write-offs as a percentage of sales per category and region; (2) logistics and handling costs per unit returned; and (3) unsellable stock volumes. These improvements can be valued using standard cost of goods and freight rates, providing a clear payback picture versus system and process investments. Reverse flows that lead to rework, resale in alternative channels, or donations can also be credited at realized or imputed value.

Indirect benefits include fewer audit adjustments and disputes, evidenced by lower claim leakage ratios and reduced manual reconciliation time for finance and internal audit teams. Better ageing visibility can reduce safety stocks or allow more targeted clearance promotions, improving working capital turns. Finance can structure pilots with matched control territories to isolate uplift, then roll improvements into ROI models that support wider rollout decisions and capital allocation for sustainability-related RTM enhancements.

Leading companies embed circularity metrics into ESG disclosures and internal scorecards by aligning RTM event data—on returns, collections, and redistributions—with standardized sustainability frameworks, and then elevating a small number of KPIs to the same status as traditional sell-through measures. The RTM system becomes the operational source for what later appears in integrated reports.

At the data layer, RTM transactions capture volume and type of recovered product (e.g., near-expiry stock returned from retail), packaging movements (crates, bottles, film), and final disposition codes such as refurbished, recycled, resold, or donated. These are aggregated monthly or quarterly into metrics like recovered volume as a percentage of total volume sold, refurbished packaging rate by material type, and resell or donation rate for returns. Internal performance scorecards then show these alongside fill rate, numeric distribution, and strike rate for RTM and supply-chain teams.

For external ESG disclosures, the same metrics are mapped to reporting taxonomies (such as tons of materials recovered and reused, or percentage of products subject to take-back schemes) and accompanied by methodology notes referencing RTM and ERP as data sources. Governance teams typically validate these figures through reconciliations between RTM, warehouse, and recycling vendor data, ensuring that what is reported to investors and regulators is grounded in auditable operational records.

A route-to-market platform supporting EPR and plastic-waste compliance needs to track packaging flows with the same rigor as product flows, across fragmented distributors and micro-retailers. It should capture what packaging is placed in the market, what is collected back, and how it is treated, in a way that aggregates cleanly into compliance reports.

Core capabilities include SKU- and pack-level master data that links each product to its packaging type, weight, and material category; transaction capture for packaging placed on the market with every primary and secondary sale; and structured reverse-logistics workflows to record collection of used or empty packaging during route visits or distributor pickups. The RTM system must support standardized reason and outcome codes (returned for refill, sent to recycler, scrapped) and maintain an auditable trail for each movement.

For reporting, the platform should be able to generate per-period summaries of packaging introduced and recovered, by material type and geography, and export these in machine-readable formats that can be combined with recycler certificates and ERP financial records. Role-based access and clear data lineage are important so that compliance teams can respond to regulator queries showing how each figure was derived from transactional RTM data.

In intermittent-connectivity environments, offline-first design for expiry, returns, and waste capture means the mobile app must function as a reliable local ledger that can queue events and sync them without data loss or duplication once a connection is available. Accuracy depends on robust local storage, conflict resolution, and user guidance when connectivity is poor.

Key considerations include storing batch, expiry, return reason, and quantity data locally on the device at the time of activity, with time stamps and outlet identifiers, and using lightweight validation rules that do not require live server checks. The app should support offline barcode scanning or pre-cached SKU lists so reps can quickly select the right items. When connectivity resumes, a deterministic sync engine uploads events, handles partial failures gracefully, and reconciles them against central stock and financial records using unique transaction IDs.

For ESG and audit purposes, the system must log original capture times, user IDs, and any subsequent edits, so that backdated syncs can still be trusted as evidence. Clear UI cues are also important: reps should see which visits and return events are pending sync, reducing the risk of duplicate manual entries. IT governance teams typically test offline flows rigorously in pilots, including simulated conflicts, before rolling them out at scale in rural and peri-urban networks.

Journey plans and beat design can support expiry prevention and returns without materially increasing cost-to-serve by incorporating risk-based visit frequencies and integrating pick-ups into existing calls. The emphasis is on smarter sequencing and prioritization rather than more visits.

Practically, RTM teams can tag high-risk SKUs and outlets—such as those with slow velocity or frequent returns—and design beats so these outlets are visited slightly more often or earlier in the cycle when near-expiry stock needs action. Visit objectives in SFA can include simple checks for ageing stock and pre-defined actions such as offering targeted schemes, recommending SKU swaps, or arranging returns. Reverse pickups of near-expiry stock, damaged goods, or reusable packaging can be scheduled on the same van routes used for deliveries, with the RTM system generating combined delivery/pickup manifests.

To avoid rising cost-to-serve, planners can use route-optimization tools that factor in both sales potential and expiry risk, ensuring that any extra stops or detours are justified by avoided write-offs or packaging recovery value. Over time, data on returns and expiry incidents by route provides feedback to further refine journey plans, pruning low-value, high-waste calls and consolidating pickups whenever feasible.

Incentive structures can be redesigned so that expiry reduction, returns recovery, and packaging performance contribute meaningfully to earnings, but in ways that field teams perceive as fair and controllable. This typically involves combining volume-based rewards with a small set of sustainability and quality KPIs derived from RTM data.

For distributors, incentive schemes can include bonuses tied to low expiry write-off rates relative to sales, timely closure of approved returns, and packaging return ratios in line with targets. Penalties for chronic non-compliance can be balanced by support programs such as better forecasting, stock-mix guidance, or embedded finance to fund right-sized inventories. For sales reps, individual or team scorecards can allocate a modest share of variable pay to metrics like “near-expiry stock identified and actioned,” “returns correctly recorded,” or “packaging collected vs. issued,” alongside traditional targets.

Gamification elements within RTM platforms—leaderboards, badges, and nudges—can highlight top performers on these sustainability-linked metrics without overshadowing core sales goals. Critical to success is clear communication of how metrics are calculated, and calibration so that reps are not penalized for issues they cannot influence (such as upstream production or transport damage), which would otherwise discourage honest reporting.

Promotion and trade-scheme design can be adapted to avoid creating expiry and returns spikes by incorporating stock-age and velocity data into eligibility, timing, and mechanics. RTM systems can help simulate how a scheme might affect ageing and returns before launch, using historical patterns and current inventory profiles.

Operationally, trade marketing can configure schemes that prioritize outlets holding near-expiry stock or slow-moving SKUs, while limiting order multipliers or forced bundling that exceed realistic sell-through between now and expiry. Eligibility rules can factor in days of cover and recent sell-out to prevent oversupply. RTM analytics can model scenarios such as “buy X get Y” or deep discounts, estimating how much stock will likely remain unsold by expiry date based on past uplift and seasonality, and flagging high-risk combinations.

During execution, real-time dashboards can monitor uplift vs. projected demand and flag territories where stock is building up faster than sales, prompting mid-campaign adjustments. After campaigns, post-promo analysis that includes returns and write-offs by scheme helps refine future design, moving from volume-only success metrics to a net, post-waste contribution view.

Accurate expiry and circularity analytics depend on robust master data that describes SKUs, batches, and packaging in a way that survives frequent changes in outlets, distributors, and product lines. RTM systems need consistent identifiers and hierarchies that anchor transactional data over time.

For SKUs, master data should include stable SKU codes, category and brand hierarchies, unit sizes, pack configurations, and links to corresponding ERP item codes. Each SKU record should also reference its default shelf life and relevant packaging attributes (material type, weight per unit, returnable vs. one-way). Batches need unique batch IDs, manufacturing and expiry dates, and mappings to production plants or suppliers, with clear rules on how batches roll up when products are reformulated or rebranded.

Packaging master data should define packaging types (e.g., crate, bottle, pouch), returnability, and standard conversion factors between case volumes and packaging units, so that RTM events such as sales, returns, and collections can be converted into comparable material flows. Governance processes must handle changes—like distributor reassignments or SKU rationalizations—through effective-dated mappings and historical preservation, ensuring that past expiry and recovery records still tie back to valid master data for audit and ESG reporting.

To avoid lock-in to a niche expiry or reverse-logistics solution that will not integrate later, buyers should treat expiry and circularity capabilities as extensions of the core RTM data model and integration architecture, not as isolated tools. The key is to ensure any specialized component can read and write standard RTM objects through open interfaces.

Practically, this means selecting or designing solutions that expose and consume APIs aligned with master SKUs, batches, outlets, distributors, and transactions already present in the RTM platform and ERP, rather than defining their own parallel identifiers. Integration contracts should specify how expiry events, returns, and packaging movements are synchronized, how conflicts are resolved, and how data lineage is maintained for audit. IT teams should test that the point solution can coexist with the organization’s analytics and ESG reporting stack, for example by pushing summarized metrics into an existing data warehouse or BI layer.

Procurement and architecture governance can also require that vendors support data export in open formats, document their schemas, and commit to collaboration with other partners. This reduces the risk that a small tool used in one country or category becomes a barrier to building a unified, multi-market RTM and sustainability analytics platform later.

Expiry hotspots, high-return corridors, and packaging-waste outliers can be made actionable in RTM control towers by overlaying a few intuitive risk indicators on familiar micro-market maps and territory views. The goal is to let regional managers see where to intervene at a glance, without needing to build their own analyses.

Common patterns include color-coded choropleth maps at pin-code, route, or distributor catchment level, where shades represent metrics like expiry risk (value of stock <= X days to expiry), returns rate, or packaging not recovered per case sold. Clicking on a high-risk area brings up simple ranked lists of SKUs, outlets, or distributors driving the issue, along with trend lines and suggested actions. Threshold-based alerts can highlight when a territory crosses predefined risk levels, such as expiry risk as a percentage of monthly sales exceeding a set band.

To keep users focused, dashboards typically combine these visualizations with a compact table of “top N hotspots” and basic filters for brand, channel, and time period. By integrating these views into the same control tower used for coverage and productivity monitoring, regional managers can triage both growth and waste issues from one place, escalating specific cases to supply-chain, trade marketing, or ESG teams as needed.

For CIOs, connecting RTM data on returns, write-offs, and reverse logistics to ERP and finance systems requires clear integration patterns that preserve financial integrity and auditability. The main principle is that every material movement recorded in RTM that has financial impact must correspond to a controlled posting or adjustment in ERP.

Typical patterns include batch ETL or near-real-time APIs that transfer summarized return and write-off events from RTM to ERP as credit notes, stock adjustments, or provisions, using shared master data for SKUs, batches, and cost centers. Reverse-logistics events—such as stock moving from outlet back to distributor or warehouse—are mapped to ERP movement types with appropriate valuation rules. Integration architecture often uses middleware to enforce validation, deduplication, and error-handling, ensuring that only approved and reconciled RTM events generate financial postings.

For ESG-related adjustments, CIOs may also pipe detailed event data into a data warehouse where finance and sustainability teams can derive both financial and non-financial indicators from the same source. Maintaining immutable logs, time stamps, and user IDs across RTM and ERP, combined with regular reconciliation routines, helps internal and external auditors trace each adjustment back to its operational origin and confirm that sustainability metrics and financial accounts are consistent.

Reverse logistics workflows in emerging-market CPG networks become manageable when responsibilities and SLAs are encoded directly in the RTM system, from initiation at retail to final disposition at company warehouses. The system should orchestrate who triggers which step, who transports, and who approves and receives each movement.

For near-expiry and damaged stock, workflows typically start when a rep or distributor user logs a return request in SFA or DMS with reasons, quantities, and photos. The RTM system assigns the case to a responsible distributor or company depot, generates pickup tasks on upcoming routes, and tracks acceptance or rejection with clear cut-offs and tolerance rules. Transporters—either distributor-owned or third-party—receive pickup and drop instructions, with manifests that link returned items to original invoices and batches.

Reusable packaging flows can be managed similarly: when full goods are delivered, the RTM app records packaging units left at the outlet; subsequent visits include expected pick-up quantities, and discrepancies are logged. Back at warehouses, receipt transactions in RTM or ERP confirm that goods or packaging arrived and specify final outcomes (repacked, reworked, recycled, destroyed). By tying each step to a role (retailer, rep, distributor store, transporter, company DC) and tracking cycle times and discrepancies, the RTM system clarifies accountability and reduces disputes over credits, debit notes, and compliance obligations.

An integrated RTM platform can be credibly positioned to a CPG board as an ESG risk-mitigation tool when expiry, waste, and circularity metrics are treated as audit-ready controls on physical flows, and as a commercial lever when the same data is used to reduce write-offs, improve mix, and optimize cost-to-serve. Boards respond best when sustainability indicators are embedded in core RTM economics—fill rate, write-off %, and reverse-logistics cost per case—rather than presented as a separate ESG dashboard.

The CEO should frame the RTM platform as an extension of financial governance: expiry tracking reduces P&L volatility, structured returns flows reduce fraud risk, and packaging recovery data reduces exposure to tightening EPR and plastic-waste rules. This connects ESG to risk-weighted capital allocation, credit ratings, and insurance perception, which are central to activist investors. Commercially, the same platform should highlight SKU- and channel-level improvements such as lower near-expiry discounting, higher realized gross margin in high-rotation outlets, and better promotion ROI because schemes are planned with expiry curves, not just volume targets.

To withstand activist and regulator scrutiny, CEOs should insist that expiry and waste metrics in the RTM stack link back to verifiable events: time-stamped visit logs, batch-level scan or manual capture, geotagged returns, and destruction/recycling certificates. A pragmatic positioning is: “This platform converts expiry and waste from opaque, manual adjustments into a governed, data-driven loop that both protects our license to operate and releases trapped margin in our route-to-market.”

First-wave sustainability use cases in CPG RTM need to sit directly on existing sales and distribution workflows and pay back within one to two quarters. Most organizations start with a narrow SKU set and a few high-volume channels, using existing SFA and DMS rails rather than new ESG processes.

Typical quick-win patterns include reducing expiry in top SKUs by tagging near-expiry batches in the RTM system and pushing simple rules to field teams: prioritize sell-through in high-rotation outlets, swap stock between nearby outlets, and trigger early discounting in wholesale channels instead of last-week dumping. Another pragmatic use case is tightening returns and damage capture for specific channels such as key distributors or modern trade: standardizing reason codes, enforcing photo or document evidence, and linking approvals to geotagged visits to cut fake or inflated returns.

These use cases usually show impact as reduced write-offs in finance reports, improved lines-per-call and mix in SFA, and lower reverse-logistics cost on select routes. Because they operate at the intersection of expiry, promotions, and route planning, they also create the data foundation for more advanced circularity initiatives (e.g., packaging recovery or reverse-logistics optimization) without overwhelming the field with new complexity.

Legal and compliance teams in CPG firms should require RTM vendors to formalize how expiry, returns, and waste-related events are recorded, stored, and made auditable, because these data points increasingly underpin ESG claims and regulatory reporting. Contractual provisions need to align RTM practices with the company’s global data-retention, audit, and EHS policies.

Key expectations typically include explicit data-retention periods for transaction, returns, and destruction/recycling records, with options for extended retention for ESG and regulatory purposes; immutable audit trails that capture who initiated, approved, and processed returns or write-offs, including timestamps, user IDs, and original data values; and structured evidence capture for returns and waste handling (e.g., mandatory reason codes, quantities, batch or expiry dates, and optional photo or document attachments) that can be exported for external audits.

SLAs should cover availability of historical data for regulatory inquiries, defined recovery point and time objectives for ESG-related data, and support for structured exports that align with ERP, sustainability-reporting, and EPR-compliance formats. Legal teams should also request clarity on data ownership, cross-border data transfers, and incident notification obligations where data related to disposal or recycling partners is shared via the RTM system.

Change-management plans for RTM programs must reframe expiry control, returns capture, and packaging collection as levers that make field teams and distributors more commercially successful, not as extra ESG paperwork. The most effective programs embed these tasks into existing visit, order, and claim workflows and tie them to incentives, not compliance threats.

For frontliners, expiry and returns checkpoints should be positioned as tools to avoid retailer disputes, protect incentive earnings, and reduce last-minute discounting that erodes commissions. Playbooks can specify simple visit routines: check near-expiry facings for the top SKUs, log damages with a photo, and, where relevant, record packaging pickup in the same mobile app they use for orders. For distributors, standardized returns and packaging processes can be linked to faster credit notes and cleaner claim reconciliation, which improves cash flow and reduces audit friction.

Change plans should bundle training with quick feedback loops: territory-level dashboards that show reduced write-offs and fewer disputes, recognition of teams that improve expiry or recovery metrics, and clear rules that expired or damaged stock logged correctly does not penalize their targets unfairly. This turns ESG data capture into part of “good selling” and operational hygiene, not a distant sustainability mandate from HQ.

For sustainability use cases in CPG RTM, prescriptive AI is most useful when it behaves like a disciplined planner that proposes simple, explainable actions, rather than a black-box engine that overrides commercial judgment. The focus should be on recommending stock movements, markdown timing, and reverse-logistics pickups with visible drivers and business constraints.

Useful examples include suggesting rebalancing of near-expiry stock from low-rotation outlets to nearby high-rotation ones, with clear parameters such as remaining shelf life, historic offtake, and transport cost; ranking outlets within a beat based on expiry risk and potential recovery so sales reps know which visits matter most; and proposing consolidated reverse-logistics routes for returns and packaging pickups that minimize empty miles, while respecting distributor service windows and truck capacities.

To avoid distrust, each recommendation should show the key inputs (e.g., current stock, days to expiry, past sell-through) and expected impact (e.g., write-offs avoided, transport cost change). Business teams should have manual override and feedback mechanisms, so the AI can be tuned to operational realities and local exceptions. Governance should treat these models like any other planning logic, with versioning, approval, and periodic back-testing to prove that suggestions actually reduce expiry and logistics costs.

Balanced RTM scorecards for regional leaders should integrate commercial and circularity KPIs into a single view that reflects how decisions on stocking, promotions, and routing affect both P&L and waste. The aim is to prevent expiry and recovery metrics from becoming a separate “ESG sidebar” that no one acts on.

A pragmatic design links expiry and recovery directly to route-to-market economics. For example, fill rate, OTIF, and numeric distribution can be shown alongside expiry rate (by value and units) and near-expiry exposure in the same category or brand panels. Cost-to-serve per outlet or per case can incorporate reverse-logistics and disposal costs, highlighting territories where high waste is eroding profitability. Packaging recovery rates or collection volumes can be expressed relative to sales in the same micro-market so that regions can compare “circular efficiency” instead of just volume.

Practically, most organizations start with simple combined tiles at region and brand level and enable drill-downs by distributor and micro-market for operational follow-up. The system should allow filtering by channel and pack type, so leaders can see, for example, that a specific route is profitable on gross margin but value-destructive once expiry and recovery costs are included.

Procurement teams should test sustainability and circularity modules in RTM platforms the same way they validate core commercial workflows: by forcing them through real data, real edge cases, and cross-system reconciliation exercises. A mature module will support everyday expiry and returns management under field conditions, not just polished ESG dashboards.

Due-diligence checks typically include hands-on pilots or PoCs with actual transaction and returns data from a defined region or category, verifying that expiry dashboards reflect what Finance sees in write-off reports and that returns workflows integrate cleanly with ERP credit notes. Teams should probe how customizable reason codes, packaging types, and partner attributes are, and whether new categories can be added without vendor intervention. They should also examine offline behavior: can field reps record expiry and returns reliably without connectivity and sync later without data loss?

Another critical test is reporting and audit support. Procurement should request sample exports of expiry, returns, and recovery data at SKU–distributor–period granularity and verify whether the schema aligns with existing finance, EHS, and ESG-reporting templates. Reference checks with customers using these modules at scale, not just early adopters in pilots, help distinguish mature implementations from recent ESG-driven add-ons.

In RTM environments with multiple 3PLs and recyclers, open-ecosystem capabilities are essential so reverse-logistics and packaging recovery data can flow into a single source of truth without manual stitching. The RTM platform should behave as the orchestration and reporting hub while allowing specialized partners to run their own systems.

Core capabilities usually include well-documented APIs for creating and updating returns and pickup orders, including attributes such as SKU, batch, expiry date, packaging type, quantity, and reason codes; webhooks or event streams so 3PLs and recyclers can push status updates (picked, received, sorted, destroyed, recycled) back into RTM in near real time; and standardized master data references, such as shared codes for outlets, distributors, packaging types, and transport assets, to prevent mismatches between systems.

To support ESG and regulatory use cases, the RTM platform should be able to ingest and store certificates or structured evidence from disposal and recycling partners, link them to original sales and return transactions, and expose them to analytics and reporting tools. Data-sharing agreements and role-based access need to be designed so external parties see only operationally necessary data, while the manufacturer retains the full audit trail for waste and recovery flows.

Multi-country CPG RTM programs need a harmonized but flexible KPI framework for sustainability and circularity so global reporting is comparable while local operations remain realistic and compliant. The starting point is a small, standardized core of definitions, with localized variants documented and mapped for consolidation.

Common practice is to standardize calculation logic for expiry-related KPIs, such as percentage of sales written off due to expiry, near-expiry stock exposure measured as days or value of inventory within a defined remaining shelf life, and proportion of returns classified as damage, expiry, or commercial. For packaging recovery, a global metric such as “collected or recycled packaging weight as a percentage of packaging put on market” can be set, while allowing local schemes to track additional categories or partner-specific details.

Local regulatory differences—such as country-specific EPR or waste-categorization rules—are handled by adding country-level attributes and mapping tables in the RTM and analytics layers. At group level, data is rolled up using the standardized definitions, with footnotes for local deviations. This approach lets global ESG reports show consistent curves and intensity measures while local RTM and finance teams work with the granularity and labels required by their regulators and operational partners.

When sustainability-linked incentives enter RTM scorecards, new fraud and abuse risks emerge around returns, disposal, and reverse logistics, especially in fragmented emerging-market networks. Common patterns include inflating expiry or damage returns to meet waste-reduction or collection targets, misclassifying commercial returns as damage or expiry to avoid scrutiny, and double-counting or fabricating packaging collections to improve circularity metrics.

RTM systems can mitigate these risks with structured audit trails and controls. Each return or waste event should capture mandatory, standardized reason codes, SKU, quantity, batch or expiry date, timestamp, user ID, and location, with optional photo or document evidence. Systems can enforce thresholds and exception rules—for example, flagging abnormal spikes in expiry returns for a distributor relative to historic baselines or peers, or requiring supervisor approval and photo proof for large or high-value write-offs.

Geo-fencing and route adherence data from SFA can be used to validate that returns are logged only at approved locations and during scheduled visits. Integration with ERP ensures that only RTM-documented returns result in credit notes or write-offs, reducing the scope for off-system adjustments. Analytics teams should periodically review anomaly reports on returns and recovery metrics, treating them as part of fraud-control and governance, not just ESG monitoring.

Marketing and corporate affairs teams can ground circular RTM storytelling in operational data by anchoring claims to clearly defined, auditable metrics and explaining how RTM processes generate those numbers. External audiences trust narratives that connect digital records to physical flows and show year-on-year improvement with transparent baselines.

The RTM system should provide traceable metrics such as expiry write-offs avoided in specific categories or regions compared with a documented baseline period; volumes of returned or recovered products and packaging linked to time-stamped, geotagged pickup events; and reverse-logistics efficiency improvements, such as reduced empty miles or consolidated pickups, calculated from route execution data. Storytelling should emphasize how field and distributor workflows have changed—for example, trained reps capturing expiry and returns at visit, standardized damage/expiry codes, and digital evidence supporting destruction or recycling.

When publishing case examples or sustainability reports, communications teams should reference the underlying governance: alignment of RTM data with ERP write-offs, periodic internal audits of returns and recovery data, and, where applicable, third-party verification by recyclers or auditors. This positions circular RTM results as part of the company’s control framework, not marketing embellishments, reducing the risk of greenwashing accusations.

Finance leaders in emerging-market CPGs can mainstream expiry, returns, and waste into RTM dashboards by representing them as cost and risk drivers within the P&L, not as side ESG metrics. The practical design is to extend existing financial views with expiry and reverse-logistics dimensions that are granular enough for action yet reconcilable with ERP.

At a minimum, RTM dashboards should show write-offs due to expiry and damage by brand, SKU group, region, and key distributors, tied back to ERP journal entries. Reverse-logistics costs—including transport, handling, disposal, or recycling fees—should be allocated to routes, distributors, or channels so cost-to-serve calculations incorporate waste. Packaging waste and recovery can similarly be expressed as intensity metrics (e.g., grams of unrecovered packaging per case sold) alongside contribution margin.

SKU–distributor–micro-market granularity is often achievable for key categories if master data is disciplined and RTM and ERP use consistent outlet and SKU identifiers. To avoid overcomplicating reconciliations, many companies limit full-detail expiry and waste tracking to priority SKUs or risk-prone categories and aggregate the long tail. The RTM system should provide drill-down from regional financial summaries into operational views—by territory manager, route, and promotion—so finance and sales can jointly act on high-risk pockets while maintaining clean reconciliation with statutory reporting.

Modernizing RTM in India and Southeast Asia to integrate sustainability KPIs requires small but precise changes in field and distributor workflows so expiry, damage reasons, and packaging disposition are captured reliably at the point of activity. The guiding principle is to extend existing order, visit, and claim routines rather than introduce standalone ESG processes.

For field reps, visit flows in SFA should include structured steps to scan or select SKUs with near-expiry or damage, capture batch or expiry dates, and tag standardized reason codes (expiry, handling damage, retailer return, etc.), optionally with a photo. Where packaging collection is in scope, the same app can record quantities or weight of collected materials by type. For distributors, DMS workflows should support batch-level stock and return registration, link returns to original invoices, and record subsequent disposition (restock, rework, destruction, recycling) with appropriate documentation.

To bring these data into daily decision-making, RTM analytics should surface expiry risk dashboards at territory and distributor level—highlighting outlets with high near-expiry stock, SKUs with repeated damage, or routes with low collection consistency. Routine performance reviews and beat-planning discussions should reference these insights alongside traditional KPIs like fill rate and strike rate, so sustainability indicators become part of operational conversations rather than periodic ESG surveys.

Embedding expiry and waste reduction into RTM KPIs without undermining volume incentives requires carefully balanced structures that reward prevention and responsible handling instead of simple “waste reduction” counts. Effective models align sales reps and distributors around sell-through quality, not just tonnage.

For sales reps, one pattern is to keep core volume and numeric distribution incentives intact but add modifiers tied to expiry exposure and discounting—for example, a bonus uplift when near-expiry write-offs and deep-discount volumes remain below a threshold in their territory, adjusted for category norms. Reps can also earn points for proactive actions logged in the RTM system, such as relocating near-expiry stock to higher-rotation outlets or triggering timely promotions, measured by reduced write-offs relative to baseline.

For distributors, incentives and rebates can incorporate clean returns behavior and packaging recovery. Rather than penalizing every return, programs can distinguish between timely, justified returns and late or excess expiry, offering better commercial terms to partners who maintain low expiry rates and provide reliable packaging recovery data. All schemes should be supported by RTM-based audit trails—reason codes, timestamps, and quantities—so Finance can verify that improvements in expiry and waste metrics reflect genuine operational change, not reclassification or channel shifting.

An RTM management system can link reverse-logistics flows to Scope 3 emissions and waste KPIs in an audit-ready manner by treating each return, rework, destruction, or recycling event as a structured, traceable transaction connected to the original sale. This turns circularity from an aggregate estimate into a chain of evidence.

Operationally, the RTM system should capture for each event: SKU and packaging type, quantities, batch or expiry dates, reason codes, location, and timestamps; transport details for reverse logistics such as distance, vehicle type, and load characteristics; and disposition outcomes (reworked, donated, destroyed, recycled) including, where possible, references to certificates or confirmations from third-party providers. These records can then be exported or fed into emissions-calculation tools that apply emission factors for transport, processing, and avoided production.

To withstand regulatory scrutiny, Finance and Sustainability teams should ensure that RTM-derived waste and reverse-logistics volumes reconcile with ERP write-offs and physical inventory movements, and that methodologies used to translate RTM data into Scope 3 metrics are documented and consistent across periods. Periodic internal or external audits of sample flows—from outlet or distributor back to processing or recycling—help validate that reported improvements in waste and circularity are grounded in actual field behavior rather than assumptions, mitigating greenwashing risk.

When circularity metrics enter RTM programs, IT and data-governance teams must treat expiry, return reasons, and packaging types as core master data, not auxiliary fields. Their role is to define standard schemas, steward reference lists, and enforce integration discipline across DMS, SFA, and ERP so sustainability data does not fragment into incompatible local variants.

Governance responsibilities include defining canonical attributes and code sets for expiry and batch data, return and damage reason codes, disposal and recovery outcomes, and packaging materials and formats; ensuring that these master data objects are managed centrally (or via a controlled hub) and synchronized to RTM and ERP systems so that events recorded in SFA or DMS align with how Finance books write-offs and how Sustainability reports waste and recovery.

To avoid long-term “regulatory debt,” governance teams should document how new ESG-related fields are added, versioned, and deprecated; prevent uncontrolled proliferation of free-text categories; and require that reporting definitions for circularity KPIs reference the same underlying masters across countries and business units. Periodic data-quality checks—such as monitoring for excessive use of “other” reason codes or inconsistent packaging-type usage across regions—help catch schema drift early before it contaminates regulatory disclosures.

To cut write-offs in high-expiry categories, CPG manufacturers can adapt micro-market segmentation and beat design so that high-risk SKUs flow preferentially through outlets with strong rotation and appropriate cold-chain conditions. The RTM system then needs to surface expiry risk at a granular level and feed it into territory planning.

Segmentation should classify micro-markets and outlets by historical offtake velocity for specific categories, reliability of refrigeration or storage, and return behavior. High-rotation, cold-chain-reliable outlets can be prioritized for short-shelf-life products, while lower-rotation or infrastructure-poor outlets receive more conservative allocations. Beat design can cluster high-risk outlets into routes that allow for more frequent visits and monitoring, while limiting exposure in remote or logistically expensive segments.

Expiry risk dashboards at the territory manager level should combine current inventory and days-to-expiry (where available) with historical sales velocity and returns data, highlighting SKUs and outlets with the highest predicted write-off risk. These dashboards become inputs into dynamic route and allocation decisions, helping managers shift stock, adjust trade promotions, or tweak drop sizes before expiry turns into write-offs. Integration with SFA and DMS ensures that decisions taken in planning are visible in execution and in eventual financial outcomes.

In networks with uneven distributor maturity, a tiered governance model works best to ensure consistent capture of returns and packaging waste without overwhelming smaller partners. The manufacturer sets common data standards and minimal requirements, then layers expectations based on distributor capability and strategic importance.

At the base level, all distributors should be required to record returns and basic waste-related events in the DMS (or a lightweight companion app) using standardized reason codes and quantities linked to invoices. Training and simple SOPs should emphasize how accurate capture protects them in audits and accelerates claim settlement. For more mature or larger distributors, additional expectations can include batch or expiry-level granularity, packaging-type capture, and digital documentation of disposal or recycling.

The RTM platform can support this model with configurable forms and workflows that adjust complexity by distributor tier, while maintaining a common schema for consolidation. Periodic scorecards and reviews should focus on data completeness, timeliness, and anomaly patterns, with incentives such as faster settlements or better commercial terms for partners that consistently provide high-quality data. Positioning these measures as part of joint business planning and risk management, rather than “ESG policing,” helps reduce resistance.

When choosing between a niche expiry-and-waste point solution and a broader RTM suite with embedded sustainability KPIs, CIOs must balance specialization against integration overhead and long-term viability. In fragmented emerging-market environments, the total cost and risk of stitching multiple systems together can outweigh the functional depth of a niche tool.

A key consideration is data flow: expiry, returns, and packaging events originate in the same field and distributor workflows that drive orders, schemes, and claims. A suite that captures sustainability KPIs at the point of transaction and visit will usually offer cleaner master-data alignment and simpler reconciliation with ERP than a separate system that must ingest and enrich transaction feeds. This directly affects ESG reporting and auditability, where consistent outlet, SKU, and batch identifiers are critical.

However, CIOs should evaluate whether the suite’s circularity features are mature enough for their medium-term ESG roadmap. If immediate regulatory exposure or category-specific needs demand advanced functionality (e.g., complex reverse-logistics optimization or specialized waste-handling integrations), a niche solution may be justified, provided there is a robust API strategy, clear ownership of master data, and a roadmap to avoid long-term fragmentation. The decision should be framed in terms of lifecycle integration risk, support ecosystem depth, and the ability to evolve ESG reporting without re-architecting core RTM flows.

A CPG board can credibly showcase “circular RTM” as part of digital transformation by bundling expiry reduction, packaging recovery, and reverse-logistics efficiency into a concise narrative that connects physical flows, data governance, and financial outcomes. The RTM system becomes the backbone that turns sustainability ambitions into measurable operational practice.

Management can structure the story around three linked objectives: first, protecting value by using RTM data to predict and prevent expiry and damage, with metrics such as write-offs as a percentage of sales and near-expiry exposure trends; second, closing the loop on materials by capturing packaging and product returns through field and distributor workflows, measured as recovery ratios by category and market; and third, optimizing reverse-logistics routes to reduce empty miles and processing costs, tracked via cost-to-serve, transport emissions per case returned, and route adherence.

To maintain discipline, the same board scorecards that track fill rate, numeric distribution, and trade-spend ROI should incorporate these circularity KPIs, with audit trails back to RTM transactions and reconciliations with ERP. This integrated view allows boards to discuss growth, profitability, and ESG performance in one frame, demonstrating that “circular RTM” is not a side program but a core element of route-to-market effectiveness and risk management.

Trade-promotion design can be linked to expiry and returns outcomes using a few pragmatic benchmarks: most CPGs initially target a 10–20% reduction in expiry write-offs on promoted SKUs and a 15–30% reduction in returns from “panic” end-of-life schemes over 12–18 months, once RTM data is properly integrated. Early pilots in 2–3 focus categories often show smaller but directional gains (5–10%) within a few cycles, which is enough to start pruning wasteful mechanics.

To do this, trade marketing teams need to treat expiry and returns as core scheme KPIs, not just supply-chain byproducts. At a minimum, RTM systems should tag each scheme line with SKU, batch/age-bucket, outlet cluster, and promotion mechanic, then track for those SKUs: uplift versus baseline sell-out, expiry write-offs, and returns over the following 1–3 months. Schemes that deliver volume but also spike near-expiry returns or write-offs should be flagged as high-leakage mechanics, alongside traditional ROI measures.

A practical operating pattern is to use RTM analytics to classify promotions into a simple portfolio: healthy accelerators (high uplift, low waste), neutral, and expiry dumpers (visible in expiry heatmaps and returns dashboards). Trade marketing can then set rules such as limiting “expiry dumpers” to controlled liquidation windows, constraining them to specific channels (e.g., wholesale vs key accounts), or replacing flat deep discounts with targeted bundles, range-selling nudges, or Perfect Store tasks that move stock earlier in the lifecycle. In both traditional and modern trade, this shifts the mix toward promotions that pull stock steadily rather than create last-minute end-of-life spikes.

Sustainability and circularity metrics can usually be embedded into existing RTM KPIs and dashboards within one or two quarters if the RTM and ERP data models are already stable. Most organizations start by adding a small set of expiry and waste indicators into existing control towers—such as expiry write-off value, damaged goods returns rate, and basic packaging recovery counts—rather than building parallel ESG dashboards from scratch.

In practice, the fastest path is to piggyback on existing DMS and SFA transactions. Distributor credit notes, return invoices, and van sales return entries can be extended with mandatory reason codes (expiry, damage in transit, packaging-only return) and simple packaging fields (unit type, approximate weight or count). These enriched records can then be surfaced in RTM analytics as trendlines and heatmaps by region, distributor, and brand, and linked to cost-to-serve and trade-promotion KPIs for activist investor reporting.

Quick-win use cases that typically show meaningful improvement within a quarter or two include: tightening return reason-code discipline to reduce “miscellaneous” write-offs; introducing expiry risk flags and near-expiry liquidation tasks for field teams in a handful of high-velocity SKUs; and piloting simple reverse logistics routes from a few large distributors to central hubs for damaged and packaging returns. These pilots often yield visible reductions in avoidable write-offs and better documentation of recovered stock, which can be credibly reported as early ESG impact while larger circularity programs scale.

In emerging-market CPG RTM operations with intermittent connectivity, essential offline-first capabilities for expiry, returns, and packaging data capture include full local storage of transactions on the device, business-rule validation without network access, and robust conflict resolution once sync resumes. Field reps and van sales teams must be able to record returns, expiry dates or age buckets, reason codes, and basic packaging details even on long routes with zero connectivity.

Operationally, mobile SFA and van-sales apps should allow: offline creation of invoices and credit notes that include return and packaging fields; scanning or manual entry of batch/expiry or age-bucket selection; attaching photos as supporting evidence; and simple picklists for return reasons and packaging categories. Sync should be incremental and resilient, so that partial uploads do not corrupt records and retry logic is automatic, with clear status indicators for unsynced transactions that may affect accounting or ESG reporting.

IT teams evaluating vendor claims about sync robustness and data integrity should insist on hands-on field tests rather than slideware. Key checks include: how the app behaves through multiple offline–online cycles; what happens when the same outlet or SKU is updated by different users before sync; how audit trails record original and edited expiry/returns entries; and whether sustainability-related fields (expiry flags, waste categories, packaging volumes) are part of the standard data model flowing into the central RTM warehouse, not a separate, fragile module. Log files, error dashboards, and reconciliation reports between mobile, DMS, and ERP are strong indicators of whether sustainability records will stand up to audit scrutiny.

To integrate reverse logistics into day-to-day distributor processes without slowing billing and dispatch, RTM operations teams should design simple, standardized return workflows that piggyback on existing DMS documents. The principle is to capture just enough structured data for ESG reporting and cost-to-serve analytics, while keeping the primary transaction flow (order, pick, invoice, dispatch) almost unchanged.

A practical pattern is to use a single, streamlined returns document type or reason-coded credit note in the DMS with mandatory fields for: outlet ID, SKU, quantity, broad reason (expiry, damage, packaging-only), and disposition (rework, destruction, recycling). Detailed information such as batch/age buckets, photos, and packaging type can be optional but encouraged, especially for higher-value items or regulated categories. These entries should be created at the same touchpoint as today’s manual returns (during delivery, during van collection, or at distributor counter), with pre-configured templates and short picklists to minimize typing.

To protect throughput, many organizations separate the physical flow from the final ESG classification: the distributor captures a basic, validated returns entry at the time of receipt, and back-office staff complete missing classification fields in batch at day-end. Control-tower dashboards then aggregate returns cost, expiry risk, and packaging recovery per distributor and route, which supports both sustainability reporting and cost-to-serve analysis without adding friction at the loading dock.

In CPG organizations where field teams already feel over-monitored, sustainability-linked RTM KPIs need to be introduced as enablers of better selling, not additional surveillance. Management should frame expiry risk flags, returns capture discipline, and packaging audit scores as tools to protect reps from future disputes and to unlock incentives, rather than as punitive controls.

Behaviorally, this works best when the first wave of KPIs is simple, transparent, and directly tied to outcomes reps care about—such as fewer retailer complaints, reduced write-offs that might otherwise cut incentives, or gamified rewards for clean shelves and timely near-expiry actions. Embedding expiry risk and returns alerts into existing SFA workflows, Perfect Store checklists, or route-planning screens keeps focus on core tasks: visit the right outlet, sell the right mix, and prevent loss, rather than asking reps to manage a separate ESG app.

To reduce gaming, RTM leaders should avoid binary “pass/fail” sustainability KPIs and instead use trend-based and peer-relative measures, backed by occasional photo or scan-based evidence. Joint KPIs across sales and supply chain—such as reduction in near-expiry stock at outlet, or improvement in first-time-right returns recording at distributor—discourage finger-pointing. Sharing clear, before-and-after territory metrics in control-tower reviews reinforces that sustainability-linked KPIs are part of running a clean, efficient business, not a new layer of inspection.

To provide a traceable chain-of-custody for expired and damaged stock, RTM systems should be configured so that every movement—from retailer pickup through distributor handling to destruction or recycling—is logged as a dated, user-attributed transaction with linked documents and evidence. Legal and compliance teams in CPG companies need outlet-level return records in the DMS or SFA, movement records in distributor stock ledgers, and final disposition records that can be tied to destruction certificates or recycling partner acknowledgments.

Operationally, this means using structured return transactions at pickup with outlet ID, SKU, quantity, reason (expiry, damage, recall), and where possible batch or age bucket; internal stock-transfer or quarantine movements at the distributor level; and final outflow documents that specify whether stock was destroyed, donated, reworked, or sent to certified recyclers. Each stage should support attaching or referencing digital artifacts such as photos of damaged goods, signed pickup notes, and scanned certificates from waste-management vendors.

For regulators and insurers, audit trails must be searchable by SKU, batch or date range, geography, and recall incident. RTM analytics and control-tower dashboards can then reconstruct the full path of affected goods, from primary shipment down to retail and back, with time-stamped evidence at each node. Ensuring that these records are retained according to local regulation timelines and that they reconcile with ERP financial postings strengthens both regulatory defense and claims with insurers for destroyed or recovered stock.

When a CPG company sets simultaneous targets for cost-to-serve reduction and improved sustainability in RTM, leaders need analytical frameworks that expose the economic and environmental trade-offs of route design and delivery cadence. A practical approach is to build a route-level and SKU-level P&L that integrates cost-to-serve metrics (drop size, distance, frequency) with expiry and packaging recovery KPIs.

In RTM analytics, this translates into dashboards and models that compare scenarios: for each route or micro-market, what happens to cost per case, expected expiry write-offs, and packaging-return ratios if the company shifts from weekly to bi-weekly drops, consolidates routes, or introduces hub-based backhauls. Key RTM KPIs include cost-to-serve per outlet and per case, expiry loss as a percentage of sales by route and channel, near-expiry stock days on hand, returns rate, and packaging recovery rate relative to shipped volume.

Frameworks such as marginal cost versus marginal waste saved, or route-level contribution after expiry and reverse-logistics costs, help operations leaders prioritize interventions. For example, shortening routes and cutting frequency may reduce fuel and time but can increase expiry risk on slow-moving SKUs; conversely, targeted additional drops in high-waste clusters can decrease write-offs enough to offset extra logistics cost. Embedding these trade-off views into control towers supports fact-based decision making instead of reactive responses to individual distributor or sales escalations.

Procurement teams sourcing an RTM platform that supports sustainability and circularity should hard-code data ownership, long-term access, and interoperability into contracts. The goal is to ensure that expiry, waste, and packaging records remain accessible and portable as ESG expectations and reporting tools evolve.

Contracts should explicitly state that the manufacturer owns all transactional and derived data, including expiry flags, returns histories, and reverse-logistics flows, and that the vendor must provide full export capabilities in open formats (for example via APIs or scheduled data dumps) for the entire retention period. SLAs should include commitments on data availability, historical depth, and recovery times for core RTM and sustainability-related data domains, not just generic uptime.

To avoid future lock-in, procurement should insist on documented, stable APIs for accessing historical expiry and waste records, clear schema documentation, and the right to integrate third-party ESG reporting tools. Clauses covering exit and migration—such as bulk extraction of all historical RTM and sustainability data at the end of the contract in a structured format—reduce risk if regulatory or investor pressure later requires moving to more advanced ESG platforms. Aligning these safeguards with CIO and sustainability teams’ governance standards helps ensure the RTM platform can keep pace with tightening circularity norms.

Executives can distinguish real sustainability improvements in RTM from mere reporting changes by triangulating operational KPIs, financial impacts, and data-quality indicators over time. Genuine improvements in expiry management and packaging recovery typically show consistent trends across outlet-, distributor-, and route-level metrics, along with corroborating changes in cost-to-serve and write-off lines in the P&L.

In practice, board-level dashboards should separate data-quality uplift (for example, reduction in “unknown” return reasons, better coding of damaged stock) from operational uplift (such as fewer near-expiry cases at outlets or higher packaging collection rates). RTM analytics can flag periods where reporting processes changed—such as rollout of mandatory reason codes or new fields in DMS—so that jumps in sustainability metrics during those windows are clearly labeled as classification improvements rather than underlying performance gains.

Executives should also rely on targeted deep dives in a few representative regions: before-and-after expiry heatmaps, route economics that factor in waste reduction, and pilot results from reverse logistics initiatives. When communication to boards and investors highlights both improved measurement and specific operational changes—like altered delivery frequencies in high-waste clusters, new trade-promotion rules for near-expiry stock, or hub-based packaging recovery models—the narrative is more credible and less vulnerable to future scrutiny.

For regional sales managers in CPG, the most practical way to embed expiry risk and returns patterns into daily RTM cockpits is to surface them as simple, prioritized alerts directly alongside core volume and distribution KPIs, not as separate ESG dashboards. Managers need expiry and returns insights that translate into clear, route-level actions rather than dense sustainability reports.

A pragmatic design is a territory view within the control tower or SFA manager app that shows a compact list of “risk clusters”: outlets or beats with high near-expiry exposure, abnormal returns spikes, or repeated write-offs, ranked by potential value at risk. Each cluster should come with recommended actions such as targeted promotions, extra visits, or SKU mix adjustments, using the same language and cadence as existing strike-rate or numeric-distribution reviews.

At the field-rep level, expiry risk can be embedded in journey plans and Perfect Store checklists—flagging specific stores and SKUs where tasks like facing correction, additional display, or liquidation offers are needed. Managers then monitor a small set of sustainability-linked execution KPIs, such as “near-expiry actions completed” or “expiry risk reduced” in key outlets, integrated into their existing performance scorecards. This keeps attention on sell-through and coverage while turning expiry and returns into manageable execution levers, not parallel objectives.

Emerging-market CPG RTM transformations that sustain focus on circularity typically rely on governance structures that embed expiry, waste, and reverse logistics into core commercial routines rather than treating them as side projects. Effective models often combine an RTM Center of Excellence with cross-functional sustainability squads and shared KPIs across sales, supply chain, and finance.

The RTM CoE acts as the process and data owner, responsible for defining expiry and returns data standards, maintaining control-tower dashboards, and coordinating changes to SFA, DMS, and trade-promotion rules. Cross-functional sustainability squads—drawing members from sales operations, logistics, finance, and ESG teams—meet on a regular cadence to review expiry heatmaps, reverse-logistics performance, and packaging recovery rates, and to decide on targeted interventions such as route changes or scheme redesigns.

Shared KPIs are crucial to prevent drop-off after the initial project. For example, combining expiry-loss percentage and on-shelf availability into sales-region scorecards; linking distributor scorecards to both fill rate and returns/packaging-handling discipline; and tying a portion of supply-chain and commercial bonuses to waste-reduction targets validated through RTM analytics and financial reconciliations. When circularity metrics are hard-wired into business reviews and incentive structures managed by these governance bodies, focus is more likely to persist beyond the first couple of quarters.

Senior sales or RTM leaders in emerging markets should redesign KPIs and distributor scorecards so that expiry risk, returns, and packaging waste appear as integrated dimensions of route-to-market health, not as separate ESG add-ons. The aim is to keep the salesforce focused on growth while making it clear that unmanaged waste directly erodes contribution and distributor trust.

A practical approach is to extend existing scorecards with a small number of waste-related indicators that tie directly to commercial performance. For field teams, alongside numeric distribution, strike rate, and fill rate, managers can track expiry-related metrics such as near-expiry stock days on hand in priority SKUs and value of write-offs as a share of territory sales, with thresholds that trigger targeted coaching rather than blanket penalties. For distributors, scorecards can combine OTIF and inventory health with returns rate by reason, claim settlement timeliness, and basic packaging-handling or reverse-logistics compliance.

To avoid demotivation, leaders should phase targets gradually, start with visibility and peer benchmarks, and use positive reinforcement—like recognizing territories that reduce expiry losses without sacrificing volume. Linking a portion of incentives to balanced scorecards that include both growth and waste metrics, and using RTM control-tower insights to distinguish structural issues (for example route design, portfolio fit) from poor execution, helps maintain a growth mindset while embedding accountability for expiry and packaging waste.

For CPG manufacturers in India, Southeast Asia, or Africa, reliable monitoring of expiry risk, damaged goods, and packaging waste in an RTM system depends on simple, resilient data-capture mechanisms at both distributor and outlet levels. These mechanisms must work with intermittent connectivity and low digital maturity, often relying on mobile-first workflows and minimal additional effort from users.

At distributor level, DMS or mobile DMS tools should capture structured return and adjustment transactions that include outlet ID, SKU, quantity, high-level reason codes (expiry, damage, packaging-only), and optional batch or age buckets. Simple photo attachments can provide evidence where batch tracking is weak. Van sales and route-based models can add returns and packaging pick-up lines directly into delivery or collection documents to avoid separate forms.

At outlet level, SFA apps can incorporate expiry checks and basic waste-related questions into Perfect Store audits or routine call forms: for example, ticking if near-expiry stock is present, scanning or entering simplified expiry buckets (0–30, 31–60 days), and confirming collection of empty packaging for specific categories. All of this must be fully offline-capable, with data stored locally until sync and validated via pre-loaded product and outlet masters. Over time, as digital maturity improves, more granular fields such as batch codes and packaging weights can be gradually introduced without overwhelming frontline users.

Finance and sustainability teams can quantify the P&L impact of integrating expiry tracking, returns, and reverse logistics into RTM by linking improved visibility to three value levers: reduced write-offs, optimized cost-to-serve, and better trade-promotion ROI. The key is to baseline these metrics before RTM changes and then attribute measurable shifts to specific operational interventions enabled by the new data.

First, they should use historical RTM and ERP data to estimate current expiry and damage losses as a percentage of net sales by category and channel, along with average returns handling cost per case. Once expiry tracking and reverse-logistics workflows are live, they can compare expiry write-offs, returns volumes, and route-level margin after waste over equivalent periods, adjusting for sales growth and mix. The difference—validated by finance through reconciled credit notes and destruction or recycling documentation—represents hard savings or avoided losses.

Second, by mapping reverse-logistics flows and packaging recovery into route and distributor P&Ls, teams can identify where consolidated pickups, hub-based collection, or revised delivery frequencies reduce combined logistics and waste costs. Finally, trade-promotion analytics that incorporate expiry outcomes can demonstrate how shifting from end-of-life discounting to earlier, better-targeted schemes both preserves price integrity and lowers waste. Presenting these quantified effects in terms of basis-point improvements in margin and payback periods on RTM investments helps CFOs and boards see sustainability capabilities as drivers of financial discipline, not just compliance overhead.

In emerging-market CPG RTM, the most effective governance model for aligning sales, supply chain, and sustainability on expiry and packaging targets is one that makes waste a shared commercial outcome rather than a single function’s problem. This typically involves a cross-functional steering group, clear data ownership in an RTM CoE, and joint KPIs embedded in routine performance reviews.

The steering group—often chaired by the CSO or head of RTM operations with representation from logistics, finance, and sustainability—sets annual and quarterly targets for expiry reduction and packaging recovery at portfolio and regional levels. The RTM CoE owns the common data definitions and dashboards, ensuring that expiry, returns, and reverse-logistics metrics are calculated consistently from SFA, DMS, and ERP sources and that data-quality issues are visible to all parties.

To avoid perceptions of unfair penalization, governance should emphasize joint KPIs and issue attribution. For example, sales regions and supply-chain teams might share a target for expiry losses below a certain percentage of net sales, while sustainability ensures regulatory alignment and accurate packaging metrics. RTM analytics can help distinguish between waste driven by demand volatility, poor forecasting, route design, or in-store execution, so that corrective actions and accountability are assigned realistically. Embedding these discussions into existing S&OP, trade-promotion, and control-tower review cycles keeps circularity integrated into core decision-making rather than a parallel ESG track.

In tightly regulated CPG markets with emerging EPR and packaging norms, RTM systems should capture a minimum set of data fields and audit trails around returns, damaged stock, and packaging flows to withstand ESG-related audits over the next 3–5 years. These fields must allow companies to reconstruct what was sold, what came back, why, how it was handled, and where packaging ultimately went.

For each return or adjustment transaction, key fields include outlet and distributor identifiers, date and user, SKU and quantity, reason code (expiry, damage, recall, packaging-only), and where possible batch or age bucket. Additional fields for packaging type (for example PET, glass, flexible), approximate weight or units, and intended disposition (rework, destruction, recycling, donation) enable compliance with EPR and waste regulations. At the movement level, RTM and DMS should record transfer of returned stock and segregated packaging between locations (for example from distributor to central warehouse or recycling partner) with time stamps and responsible entities.

Audit trails should log creation, modification, and approval of these records, including who changed what and when, and should support attachment or referencing of evidence such as photos, signed pickup notes, destruction certificates, or recycler acknowledgements. Ensuring that this data is retained in line with statutory requirements, is reconcilable with ERP financial entries for write-offs and EPR fees, and can be sliced by geography, product family, and time window positions the RTM system as a defensible evidence base during ESG-focused inspections.

A CIO can ensure new sustainability and circularity KPIs integrate cleanly with ERP, tax, and ESG systems by modeling them as extensions of existing RTM data domains rather than as a separate, isolated data mart. Expiry risk indices, reverse-logistics recovery rates, and packaging collection ratios should be derived from standard transactions—sales, returns, stock movements, and promotions—so they share master data, hierarchies, and reconciliation rules with finance and tax reporting.

Architecturally, this means enhancing the RTM data warehouse or lake with additional fields on existing tables (for example reason codes, expiry buckets, packaging attributes) and defining KPI calculation logic in a semantic layer that can feed multiple consumers: control towers, ESG dashboards, and ERP-side analytics. The same outlet, SKU, distributor, and territory masters used for revenue and cost-to-serve should anchor sustainability metrics, ensuring that cross-system joins remain straightforward and auditable.

Integration with ERP and tax systems typically involves standardized interfaces that transmit summarized and, where needed, transactional information on write-offs, returns, and packaging flows, aligned with chart of accounts and tax schemas. For ESG reporting tools, APIs or data feeds from the RTM warehouse should expose curated sustainability views, not raw, duplicative datasets. Governance processes—covering data lineage, change control for KPI definitions, and periodic reconciliations between RTM, ERP, and ESG outputs—help prevent drift and maintain a single source of truth across operational and compliance reporting.

For a CPG manufacturer currently tracking only primary and secondary sales, a pragmatic roadmap to add expiry and reverse-logistics analytics is to layer capabilities in stages, focusing first on high-impact visibility and simple interventions before expanding into advanced dashboards. The objective is to avoid overwhelming middle management while still moving toward expiry heatmaps, proactive liquidation, and reverse-logistics views.

Stage one focuses on data capture and basic reporting: introduce structured reason codes and optional expiry/age-bucket fields into existing return and adjustment flows in DMS and van-sales; configure a simple expiry-risk view that approximates near-expiry inventory using days-of-stock and age assumptions where batch data is weak; and add a single waste summary panel into current control towers showing write-offs and returns by region and category.

Stage two adds targeted actionability: build expiry heatmaps by micro-market for a handful of priority SKUs; configure near-expiry liquidation tasks and trade-promotion triggers in the RTM system for those SKUs; and surface a basic reverse-logistics flow view showing volumes and costs of returns from key distributors. Only in stage three should the organization roll out more granular reverse-logistics dashboards and sustainability scorecards, after field teams and middle managers are comfortable with incorporating expiry and returns indicators into their regular performance discussions.

A Chief Sales Officer can recalibrate trade-promotion design so that near-expiry liquidation is proactive and brand-aligned by embedding expiry logic directly into scheme rules within the RTM management system. The goal is to trigger controlled, targeted actions well before panic discounting is needed, using mechanics that protect price positioning.

Practically, this means segmenting SKUs by lifecycle and expiry profile, and using RTM analytics to identify typical points where expiry risk spikes by channel and micro-market. Scheme templates can then incorporate eligibility conditions linked to inventory age buckets or near-expiry flags: for example, offering modest, channel-appropriate incentives or value-added bundles when stock enters a defined “amber” window, rather than deep price cuts in the final weeks. Promotions can also be restricted to specific outlets or routes with documented risk, avoiding broad brand-wide discount signals.

RTM systems that tie trade promotions to outlet-level stock indicators and Perfect Store execution tasks allow field reps to execute these early interventions as part of normal calls—for instance, applying display incentives, secondary placement rewards, or range-selling nudges that prioritize at-risk SKUs without overt discounting. Control-tower dashboards and scheme-ROI reports should then track both uplift and expiry outcomes, so that the CSO can iteratively adjust scheme parameters and channel targeting to balance sell-through objectives with long-term brand equity.

In fragmented RTM networks with many small distributors, practical reverse-logistics models tend to favor simple, scalable patterns that can be orchestrated through the RTM system without heavy infrastructure. Two common models are hub-based collection and backhauling via van sales, both of which can be managed through DMS and SFA workflows.

In a hub-based collection model, smaller distributors accumulate expired or damaged stock and, where feasible, segregated packaging. Periodically, this material is consolidated to regional hubs or central warehouses for disposal, recycling, or rework. The RTM system supports this by enabling standardized return transactions at the distributor, stock transfers to hubs, and final disposition records tied to destruction or recycling documentation. Control-tower views can then show recovered volumes and write-off values by hub and region.

Backhauling via van sales leverages existing delivery routes: field trucks collecting returns and packaging on their way back from outlets or small distributors, recording these pickups as additional lines on delivery or van-sales documents. This minimizes incremental logistics cost and fits naturally into route planning. RTM route-optimization and territory-planning modules can designate specific days or routes as “collection-heavy,” balancing capacity, visit compliance, and recovery targets. By modelling these flows in the RTM platform and linking them to cost-to-serve and expiry-loss metrics, operations leaders can gradually scale reverse logistics in a way that reduces write-offs without overburdening small distributors.

The most effective change-management tactics for adding returns, damages, and packaging-collection fields into SFA/DMS are those that minimize extra effort, link the data to rep incentives, and use simple guardrails against gaming. Programs work when the new fields are positioned as tools to protect rep incentives and distributor margins, not as extra compliance.

Operations leaders typically start by redesigning the workflow so most new data is captured passively: pre-filled SKU lists, default reasons, photo scans instead of long forms, and barcode or QR scans for packs. This reduces tap-load and lowers the chance that reps will skip or fudge entries. Training is delivered as short, beat-level huddles showing concrete benefits such as fewer debit notes, faster claim settlements, and reduced disputes on expiry write-offs.

To avoid resistance, targets and incentives are phased: for an initial period, reps and distributor staff are measured on completeness and timeliness of returns data, not on lower expiry. Gamification and control towers are used to flag obvious anomalies (e.g., identical quantities across outlets, returns without matching sales, or zero-damage reporting in high-risk categories). Middle managers receive simple exception reports so they can coach, not just penalize. Over time, once data quality stabilizes, the same records are used for more advanced KPIs like expiry incidence, reverse-logistics turnaround, and packaging-recovery ratios.

An RTM management system can support board-level ESG scrutiny by treating expiry losses, returns, and packaging recovery as tagged financial events within the same data model as primary and secondary sales, not as separate sustainability logs. When each write-off, return, or collection is coded with both P&L dimensions and ESG attributes, the board can see waste and circularity impacts inside the standard control-tower and finance dashboards.

In practice, finance and RTM operations teams align on a shared taxonomy: reason codes for returns and expiries; material codes for recyclable vs non-recyclable packaging; and mapping tables that link SKUs to packaging types and weights. The DMS captures these attributes at transaction level, and the RTM analytics layer aggregates them into expiry loss value, write-off rate by channel, and packaging recovered vs sold, all reconciled against ERP. Board views then show waste cost as a percentage of net sales, provisions for expiry alongside gross margin, and recovery ratios per region next to OTIF and fill-rate metrics.

This integration allows CFOs to narrate ESG performance as part of working-capital management, cost-of-waste, and distributor health, rather than a standalone ESG slide. Governance teams typically add audit trails, frozen cut-offs, and reconciliation reports so that ESG and financial figures are provably sourced from the same RTM transaction base, reducing accusations of cherry-picking or parallel reporting.

In emerging-market CPG RTM, benchmark ranges for circularity metrics vary widely by category, channel mix, and cold-chain maturity, so most organizations use relative and trend-based thresholds rather than universal “good” numbers. Leadership teams monitor deviations from internal baselines and peer clusters to detect outliers or fraud, more than fixed global targets.

For expiry incidence, manufacturers often track value of expiries as a percentage of secondary sales by category and channel; ambient products in general trade may tolerate low single-digit percentages, while chilled or short-shelf-life categories accept higher baselines. Return rates are segmented by SKU and reason code, with attention to sudden spikes in damage or quality claims in specific distributors, which can indicate misuse or stock rotation issues. Packaging-recovery ratios are typically benchmarked relative to pilot regions with organized reverse logistics rather than global figures, since infrastructure and regulation differ.

Control towers flag outliers using z-scores or percentile bands at distributor and territory level, combined with qualitative context like recent price changes, scheme launches, or route redesigns. A common pattern is to pair these circularity indicators with distributor profitability, claim velocity, and strike-rate metrics so that anomalies are assessed in an operational and fraud-risk lens, not in isolation.

A CPG company can standardize sustainability and circularity KPIs in multi-country RTM by defining a global data model and KPI formulas, while allowing local markets to adjust thresholds, SLAs, and workflows through configuration. The key is to separate what is measured (expiry, reverse-logistics time, packaging collection) from how fast or how much is acceptable in each market.

Head office typically defines a common “expiry event” schema, standard reason codes, and core measures such as expiry value as a percentage of secondary sales, reverse logistics turnaround time from retailer request to credit note, and packaging collected vs sold by material type. These are implemented as global fields in the DMS/SFA and RTM analytics layers, with shared logic for how events roll up to dashboards. Local teams then configure target bands, routing rules (e.g., direct van pickup vs third-party), and approval hierarchies to suit their regulatory environment, retailer behavior, and infrastructure.

Governance is managed through a central RTM CoE or sustainability office that publishes KPI definitions, minimum reporting standards, and data-quality scorecards. Country teams are allowed to add local KPIs, but not change the core definitions, ensuring that board-level “circular RTM” scorecards remain comparable, while respecting market realities such as informal returns, weak recycling ecosystems, or differing extended producer responsibility rules.

IT and procurement teams evaluating RTM platforms should probe whether expiry tracking, returns workflows, and ESG reporting are embedded in the transaction and master-data models, or bolted on as cosmetic dashboards. Due-diligence needs to focus on data structures, workflow depth, and auditability, not just on the presence of an “ESG” menu.

Critical questions include how the system models returns and expiry events: are there structured reason codes, linkage to original invoices, and automatic accounting impacts, or only generic notes? Can workflows handle common RTM realities such as partial returns, multi-tier claims (retailer → distributor → manufacturer), and photo or scan-based evidence capture? Teams should ask how packaging attributes are stored at SKU level and whether the vendor supports weight or recyclability tagging that can feed regulatory disclosures later.

On reporting, buyers examine whether ESG metrics draw directly from the same single source of truth as financial and operational KPIs, with clear drill-downs and exportable audit trails. Integration questions cover how expiry and returns are synced with ERP and if data schemas anticipate future waste or EPR rules. Finally, teams inquire about reference implementations where the platform is already used for expiry control, reverse logistics, or packaging tracking, to distinguish mature capabilities from slideware.

Prescriptive RTM algorithms that already suggest assortments and visit plans can incorporate expiry risk and reverse-logistics costs by enriching their feature set with shelf-life and return-history signals, while exposing simple, human-readable justifications alongside each recommendation. Adoption improves when regional managers see clear trade-offs, not opaque scores.

Practically, the RTM platform extends its data model to store per-batch expiry dates, outlet-level sell-through velocity, historic expiry incidence by SKU and outlet, and typical reverse-logistics cost per route. The AI or copilot then factors these into optimization objectives such as minimizing probable write-offs while maintaining numeric distribution and service-level constraints. For example, visit recommendations might prioritize outlets with high on-hand stock nearing expiry, or assortment suggestions might downgrade slow-moving SKUs with chronic expiry in certain micro-markets.

Explainability is handled through plain-language rationales (“Recommended advancing this visit by 2 days due to high expiry risk on SKU X worth $Y”) and transparent KPIs showing forecasted reduction in expiry vs incremental travel cost. Governance teams often enforce override options and logging so that managers can adjust routes or assortments while still feeding back decisions to the model, reinforcing trust and enabling continuous recalibration of expiry and logistics parameters.

An RTM system that uses returns and expiry data both for financial settlements and sustainability KPIs needs strong safeguards to prevent these events becoming a channel for leakage or fraud. Effective designs combine preventive controls in workflows, anomaly-detection analytics, and clear exception-handling paths owned by sales and finance.

At workflow level, every return or expiry claim is tied to specific invoices, SKUs, and quantities, with mandatory reason codes, geotagging, and evidence such as photos or scans. Threshold-based approvals are configured so that high-value or unusual claims require supervisor or finance sign-off, while small, routine items are auto-approved. Time-window constraints ensure returns are only accepted within realistic periods after sale, and batch or lot numbers are recorded where feasible to avoid double-claiming.

Control towers monitor patterns like repeated high-expiry claims in low-risk categories, spikes clustered around scheme changes, or returns that exceed historical norms for a distributor or territory. These trigger exception workflows that can include temporary credit holds, joint market visits, or targeted audits. Importantly, the ESG dashboards are fed from the same validated event pool, with flags indicating which events are still under investigation, so sustainability metrics are not inflated by unresolved or fraudulent claims.

In van-sales and rural RTM operations, sustainability elements such as fuel efficiency, drop sizes, and reverse pickups can be integrated into route rationalization models by adding them as additional objectives and constraints, rather than hard cuts that reduce service. The goal is to rebalance routes to improve economics and emissions intensity while protecting numeric distribution and visit frequency commitments.

Route-design algorithms in the RTM system can incorporate distance, vehicle type, fuel consumption, average drop value, and frequency of reverse-logistics tasks like expiry or packaging returns. Beats are then optimized for both revenue and cost-to-serve metrics, for example by clustering low-volume outlets into specific days or shared routes, prompting load planning to combine forward deliveries with planned reverse pickups, and identifying outlets where van sales can be supplemented by partner-distributor delivery.

Service levels are preserved by encoding minimum visit frequencies and maximum allowable gaps as constraints in the optimization model, ensuring remote outlets are not silently deprioritized. Dashboards show KPIs like revenue per kilometer, average drop size, and proportion of trips with reverse pickups, allowing operations leaders to fine-tune territory design and van allocation over time. This approach links sustainability to beat productivity and cost-to-serve rather than positioning it as a competing agenda.

In traditional trade where retailers dislike returns paperwork, RTM-enabled incentives and policies work best when they exchange minimal digital friction for clear value—such as faster credit, protection from loss, or access to schemes—without eroding margin discipline. The RTM system becomes the channel for simple, low-touch evidence capture and automatic benefit calculation.

Manufacturers commonly deploy simplified mobile flows where reps initiate expiry or packaging returns on behalf of the retailer, capturing photos and basic metadata in seconds, so the retailer’s visible “paperwork” is reduced. Incentive levers include small, transparent credits or loyalty points for timely returns, bonus eligibility tied to participation in packaging-collection programs, or prioritized delivery for outlets that meet agreed collection or expiry-reporting standards.

To maintain margin discipline, these benefits are capped and rules-based—configured in trade-promotion or scheme-management modules with clear eligibility criteria and maximum payout ceilings per outlet. Control dashboards cross-check return volumes and credit notes against secondary sales to avoid over-incentivizing returns or creating arbitrage opportunities. Over time, retailers learn that cooperating through the RTM channel reduces disputes, accelerates claim settlement, and may give them preferential access to schemes, aligning their behavior with the manufacturer’s circularity objectives.

To avoid future “regulatory debt” on waste and packaging, CPG organizations should configure current RTM systems with data structures and workflows that anticipate traceability, attribution, and auditability demands, even if current laws are light. The design principle is to capture clean, structured events now so that new ESG disclosures can be produced by configuration, not re-platforming.

Practically, this means modeling packaging attributes at SKU level (material type, weight, recyclability), standardizing expiry and returns reason codes, and logging reverse-logistics and disposal or recycling steps as distinct, timestamped events linked to outlets, distributors, and invoices. The system should store who initiated and approved each event and retain supporting evidence, creating a verifiable chain for future regulators and auditors.

Architecturally, RTM platforms should expose these data objects through APIs and analytics layers that support flexible reporting cubes, so new ESG ratios or jurisdiction-specific EPR metrics can be defined without schema rewrites. Governance teams define minimum global fields that all markets must populate, even where they are not yet mandated, and adopt data-quality scorecards. This approach embeds circularity data into the single source of truth for RTM, giving enterprises the headroom to respond quickly when waste or packaging regulations tighten.

Integrated RTM sustainability metrics strengthen an ESG and digital-transformation narrative when they are clearly tied to transactional data, financial outcomes, and operational decisions, rather than presented as standalone “green” numbers. Investors are less likely to perceive greenwashing when expiry, reverse logistics, and packaging metrics are shown with baselines, methodologies, and trade-offs.

Organizations typically build circular RTM scorecards that combine expiry incidence, waste cost, recovery ratios, and reverse-logistics turnaround with P&L measures like gross margin, cost-to-serve, and working-capital days. Dashboards allow drill-down from high-level ESG KPIs into outlet, distributor, and SKU-level events, with visible audit trails and consistent definitions across markets. Narratives to investors then highlight how RTM digitization enabled specific initiatives—such as targeted expiry-risk dashboards or optimized reverse-logistics routes—and quantify both financial savings and waste reductions.

To avoid cherry-picking accusations, companies disclose methodologies, include both improvements and problem areas, and show multi-period trends rather than single-year highlights. Finance, sustainability, and RTM operations co-sign key metrics, and control towers enforce one source of truth for ESG and financial data. Linking these metrics to executive scorecards and incentive plans further signals that circularity is embedded in core management systems, not an external reporting exercise.