Changelog

Categories: Security, Feature, Fix, Perf, Admin, Deps.

[1.1.0] - 2026-08-26

Feature

• Time-based triggers: a trigger can now fire because nothing happened, not only because a carrier scan arrived. Use it to warn a customer before a pickup point returns their parcel — no carrier announces that return, and the shop usually learns of it from the refund request.
• Ships a "Pickup Reminder" email and a pre-configured 5-day trigger, inactive like every other seeded trigger. Set the threshold against your own carrier agreement: retention runs from seven to fourteen days depending on country and contract.
• New days_in_status email variable, so a reminder can say how long the parcel has been waiting.
• Feed profiles can register parcels they do not recognise, taking the address from the file. A replacement parcel dispatched from an ERP produces no Magento shipment, so nothing else would ever create it.
• New CLI wimakeit:deliverytracking:parcel:import for the same case served differently: a list of parcels rather than a file of scans. Supports --dry-run.
• Feed profiles gained a store setting, so parcels created without an order render their emails in the right locale and from the right sender.

Security

• A carrier feed password was redisplayed in clear text when the form failed validation. It is no longer carried back into the page, and the field is masked.

Fix

• Triggers restricted to a customer group never fired, and left no trace in the notification log because the filtering happened before anything was written. They work now.
• Time-based triggers honour the repeat delay the form offers; previously it could never take effect.
• Mass actions on large selections run in batches instead of one statement, so they no longer lock tables the storefront reads.
• The Email Trigger edit form failed to open at all: it referenced a customer-group source class that does not exist in Magento. Editing a trigger works again.

Admin

• Trigger form and grid expose the dwell threshold.
• Two new settings bound the time-based scan: how many parcels each trigger examines per run, and how stale a parcel may be and still earn a reminder.

[1.0.1] - 2026-08-25

Fix

• Mass actions now respect the filters applied to a grid: selecting every row on a filtered grid no longer acts on rows outside the filter.
• "Select all" works on the Email Triggers and Status Mapping grids, where it previously did nothing at all.
• Carrier feeds can only read inside a configurable base directory, so the feed permission can be delegated safely.
• A polling run now stops on a time budget as well as a parcel count, so an unresponsive carrier cannot make it overrun its schedule.
• The per-carrier call ceiling was set above the batch size and could never take effect.

Perf

• Carrier feed files are streamed and processed one at a time, so memory no longer grows with the number of files waiting.
• Feed ingestion resolves parcels in two queries per file instead of one or two per line.
• Event ingestion is written in bounded batches, whatever history length a carrier returns.
• Parcel timelines are capped in the database rather than after reading every stored event.

Admin

• New health command reporting degraded carriers, stuck notifications, failing feeds and unmapped status codes, with a non-zero exit code for monitoring.

[1.0.0] - 2025-08-25

Feature

• Parcel tracking for DPD, UPS, bpost and Mondial Relay behind one adapter interface, each carrier enabled independently.
• Carrier status codes are translated to a canonical set of parcel statuses through an editable mapping table.
• Unknown carrier codes are captured automatically, counted, and never send an email until confirmed by an operator.
• Sixteen canonical statuses, keeping "waiting at a pickup point" distinct from "delivered" so the customer gets the right instruction.
• Generic file ingestion over CSV drops, with the column mapping stored per feed so one carrier's country variants both work.
• Adaptive polling: parcels out for delivery are checked every 30 minutes, parcels awaiting handover every two hours.
• Seven email templates with shared header and footer fragments, rendered in the store view's own locale.
• Customer account page listing every parcel with its progress, timeline and pickup point details.
• Parcel status shown on the order view page and summarised under the order history.
• Secure tracking page reachable from the emails without signing in, which guest orders require.
• Notification preference in the customer account, plus an unsubscribe link in every email.

Admin

• Tracked Parcels grid with per-row refresh, resend and tracking-link regeneration, plus mass actions.
• Email Triggers grid and form: one status to one template, with carrier, store view, customer group, delay and frequency conditions.
• Status Mapping grid with inline editing, so correcting a carrier code is a click rather than a form round trip.
• Notification log recording every send and every deliberate non-send with its reason.
• Carrier Feeds grid and form, with a run-now action reporting how many rows matched.
• CLI commands to poll parcels, run a feed and list carrier codes still awaiting mapping.

Security

• Guest tracking links use 128 bits of entropy, expire, are rate limited per IP, and expose neither the delivery address nor the order total.
• Unsubscribing requires a confirmation step, so mail security scanners that pre-fetch links cannot opt customers out.
• Carrier credentials are stored encrypted and never returned to the admin form.

Perf

• Re-reading the same carrier response inserts nothing: event ingestion is idempotent through a unique index.
• Delivered and returned parcels stop being polled; parcels with no activity are abandoned after 45 days.
• Retention cleanup deletes old events and notifications in bounded chunks, keeping the admin grids responsive.

Deps

• Requires PHP 8.1 or later, Magento 2.4.6 or later, and wimakeit/module-core 3.0 or later.