Prepare for Digital Product Passport Compliance with Expert Insight from Lora Cecere
Founder, Supply Chain Insights

With the EU Digital Product Passport (DPP) set to launch in 2027 for initial industries—batteries, consumer electronics, and textiles (footwear and apparel)—businesses are beginning to confront a rapidly evolving compliance landscape. Yet with many requirements still undefined, confusion is widespread.

Lora Cecere's latest research helps organizations cut through the uncertainty by offering actionable insights and a clear, customer-centric, outside-in approach to DPP readiness.

Key Highlights:

• Start with the Customer in Mind
  Align compliance efforts with market demands to drive growth and gain a competitive advantage.

• Break Down Silos
  Cross-functional collaboration—across sustainability, supply chain, procurement, and policy is essential for success.

• Clarify Compliance
  Understand the core elements that define DPP compliance and the practical steps needed to achieve it.

• Learn from Diverse Approaches
  See how companies are navigating DPP differently, with no one-size-fits-all path to readiness.

• Adopt GS1 Standards
  Address the existing gap in the implementation of critical global standards for traceability and product information.

Build the capabilities your organization needs today to meet the demands of tomorrow—with a forward-looking, customer-first strategy.

👉 [Access the full research here] 

1. You Can’t Track Project Costs in Real-Time
   If you're waiting until after a project wraps up to find out whether it was profitable, that’s a major red flag. Without real-time cost tracking, you're making critical decisions in the dark.

2. Quoting and Estimating Are Slow, Manual, or Inconsistent
   Does it take hours—or even days—to build a custom quote because you're pulling information from multiple systems? That lost time translates directly into lost sales opportunities.

3. You Rely on Spreadsheets for Critical Operations
   Spreadsheets are useful—until they’re not. Issues like version control problems, accidental overwrites, and human error can lead to costly mistakes.

4. Scheduling and Inventory Management Are Disconnected from Financials
   If your production and finance teams aren’t working from the same data, it’s only a matter of time before you face delays, stockouts, or budget overruns.

5. You Don’t Have a Real-Time View of Project Profitability
   Without live costing tied directly to jobs, small losses can accumulate unnoticed, until it's too late.

Disconnected data refers to information stored outside your core business systems, like your ERP. While this data has value, a lack of integration causes inefficiencies and misalignment across your organization, often more than you realize.

The Cost of Disconnected Data...

In typical LN REST API integrations, permissions and authorizations are not implemented or rarely used. To ensure smooth data exchange and avoid errors, it is recommended to disable the authorization and security settings.

Recommendation:

• In the Authorization and Security Parameters session (tcsec0100m000):

  • Clear the Authorization and Security Enabled check box.

  • Clear all check boxes under Authorization Enable for on the Enabling tab.

Why This Matters:

• Enabling authorization and security without proper setup can lead to errors and blocked transactions during integration.

• For example, work center permissions may interfere with:

  • Creating new shifts

  • Booking machine hours

  • Read more

This functionality allows you to copy the product structure of a customized item to a standard item.

Note: When a customized structure is copied to a standard structure, the Customized check box in the Items session (tcibd0501m000) is cleared.

Item Types:

• Standard Items: Identified by a regular item code.

• Segmented Items: Consist of a project code segment and an item base segment (i.e., the customized item’s item code). Segments are defined in the Item Code Segmentation session (tcibd0500m000).

Only components valid for the specified Effectivity Unit will be copied.

Copy Options:

• Target Routing Code
  Enter the code of the standard routing to which the customized structure should be copied.

• Copy Product Structure
  Choose whether to:

  • Copy the entire structure

  • Copy only the first level

  • Perform the copy interactively

• Reference Date
  Only parts of the product structure valid on this date will be copied.

• Copy E-Item Relationships
  If selected, related E-item records will be copied.

• Copy All Components and Effectivity Statements
  If selected, unit effectivity is copied to the standard structure. You can specify the unit.
  Exceptions related to routings and operations (that meet date effectivity) are also copied.

• Alternative Material
  If selected, alternative BOM components are included in the copy.

• Use-Up Material
  If selected, use-up materials from BOM components are included.

Use this session to rebuild the ledger account history for account matching. This is particularly useful if you’ve recently defined a ledger account, on which transactions already exist, as a matchable account.

You can specify the fiscal year and period for which you want to rebuild the account matching history.

Note: This session can also be used to remove unmatched transactions if you decide to stop performing account matching for a specific ledger account.

Field Information

Selection Range

• Use Job Reference Date
  If selected, Infor LN uses the Job Reference Date as the basis for rebuilding history data.

• Job Reference Date
  Specifies the date and time used for the rebuild process.
  Enabled only if "Use Job Reference Date" is selected.

• Financial Company
  The financial company for which you want to rebuild a ledger account history.

• Ledger Account
  The specific ledger account to rebuild.

• Fiscal Year
  The fiscal year for which you want to rebuild the ledger account matching history.
  
   

FINANCE: Rebuild History for Account Matching (tfgld1218m000)

OPERATIONS: Copy Customized Product Structure to Standard Structure (tipcs2232m000)

TECHNOLOGY: Authorization and Security: LN REST APIs

FINANCE: Override Warning in Invoice Entry PO Costing

OPERATIONS: Auto Calculate Vendor Delivery Date

TECHNOLOGY: User Provisioning

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

• In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

• A new “F14 to Override” warning message replaces the old message:
  “Details have changed. Press enter again to accept data.”
  This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

• “Apply GRN Costing Tolerance for PO Costing” (optional):

  • Within tolerance: Displays the original message —
    “Details have changed. Press enter again to accept data.”

  • Outside tolerance: Triggers the new override requirement —
    “F14 to Override”

Benefits:

• Enhances oversight and reduces unintentional cost acceptance.

• Enables better control of PO costs when invoice details differ from expectations.