Colisly Parcel Forwarding provides a complete client and parcel management system for a package forwarding business: receiving, storage, consolidation and reshipping of parcels (for example towards the French overseas territories). It suits forwarders, reshippers and virtual address services that already run their store on WooCommerce. The interface is in English and can be translated into any language through translate.wordpress.org.
Customers only see the information meant for them (parcel number, reception date, tracking number, weight, status, grouping allowed) in their WooCommerce My Account area: “My parcels”, “My shipments”, “My documents” and “Shipment request” (mes-colis, mes-expeditions, mes-documents and demande-expedition on French sites). Internal comments and dimensions are never displayed to customers.
Each shipment request creates a detailed WooCommerce order: one fee line per parcel, a storage fee line and the chosen carrier as a native shipping line priced from its configurable tariff (base price + price per kg). The customer is redirected to the standard WooCommerce payment page and pays with any payment gateway enabled in the shop. Statuses stay synchronized both ways: order paid shipment “paid”; shipment “shipped” order completed; order cancelled parcels returned to stock. The shipment request form shows each carrier tariff, disables carriers that are not allowed for the selection, and displays a live total estimate (parcels + storage + transport).
Two real WooCommerce e-mails are registered under WooCommerce Settings Emails: “Parcel received” (sent to the customer) and “Shipment requested” (sent to the staff, with configurable recipients). They use the shop e-mail template and can be overridden from the theme. Without WooCommerce, a plain-text fallback keeps notifications working.
Client documents and reception photos are stored in a protected directory (direct access denied, randomized file names) and served only through an authenticated download endpoint: a customer can only download their own documents marked as visible; reception photos are restricted to the staff.
The architecture is built to grow: actions and filters (colisly_parcel_created, colisly_shipment_requested, colisly_carriers, colisly_parcel_price, colisly_carrier_price, …) allow adding import/export, statistics, loyalty programs, a REST API or multi-warehouse support without touching the core.