Polymr
Adhesives · case study

Batch planning that survives a supplier delay.

Single-source resin suppliers slipped two to three times a quarter. Each slip triggered a manual cascade across batch plans, customer commitments, and AP.

Outcome
78%

reduction in supplier-delay impact on weekly batch plan.

Customer

Industrial adhesives manufacturer, single large plant

The source stack.

The systems Polymr reads from and writes back to for this workflow.

  • SAP S/4HANA
  • Vendor portals
  • Email

Result from a configured pilot on customer data.

What Polymr automated.

Supplier delay signals from inbox and vendor portal tied to affected batches in real time. Alternate vendor and substitute resin recommendation surfaced with a price-per-kg and lead-time delta for buyer approval. Batch plan rewritten before the line stops.

What this looks like inside Polymr.

The screenshot below is the live tenant view that powers the workflow described above.

/inboxSupplier delay signals at intake
Polymr procurement inbox parsing supplier delay notifications from email and portal

The supplier slipped. The batch plan held.

Two views of the same week. The left panel is what the plant saw before Polymr; the right is the same week routed through the configured pilot.

Before · Tuesday 09:00 local

Resin Vendor A slips 36 hours. Plant finds out at receiving.

  • 09:14 · Vendor A portal updates the PO line to Thursday. No alert routed.
  • 11:02 · Batch B-318 sequenced as if material lands today.
  • 14:40 · Receiving flags the missing drum. Two batches pulled.
  • 16:20 · Customer call to slip a packaged-goods commitment by 2 days.
Plan recovered manually over 3 days
After · Tuesday 09:00 local

Slip detected at the portal. Substitute scored before the line touches it.

  • 09:14 · Polymr reads Vendor A portal diff. Affected batches identified: B-318, B-322.
  • 09:18 · Vendor C resin substitute scored: +$0.18/kg, -22h lead, formulation match accepted.
  • 09:33 · Buyer approves the substitute in the review queue. PO drafted in SAP S/4HANA.
  • 10:10 · Batch plan rewritten. Customer commitment held.
Recovered in 56 minutes

“The cascade never started. The plan absorbed the slip before the line saw it.”

Pilot operator note, week 4.