Colisly Parcel Forwarding

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. Client management module

• Every client is linked to a WordPress/WooCommerce user and gets an internal record with a short unique reference (CL000001).
• Search clients by reference, first name, last name, e-mail address or phone number.
• The client record centralizes everything: client information, reference, parcels in stock, shipped parcels, shipments, transmitted documents and the full operation history.
• Automatically computed indicators: parcels currently in stock, total stored weight, shipments done, storage fees due, last parcel reception, last shipment.
• Free storage period per parcel (15 days by default, configurable), then automatic storage fees per day.
• From the client record: create a parcel, browse parcels, prepare a shipment, check documents and read the history.

Parcel creation module

• Search the client by internal reference, name or e-mail, with an immediate view of their parcels still in stock.
• Complete form: carrier tracking number, real weight, dimensions (visible to administrators only), optional reception photo, internal comment reserved for the staff, grouping allowed or forbidden, allowed carriers per parcel.
• Unique parcel number generated automatically (COL000001), reception date, creator and initial "available" status.
• Life cycle: available, ordered, awaiting payment, paid, preparing, shipped, destroyed, cancelled.
• The parcel price is computed automatically from its weight (configurable tiers) and stored at reception time.

Customer side 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. Native WooCommerce payments 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). Native WooCommerce e-mails 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. Private documents 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. Extensible 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.

1.6.7

• Fix: a parcel created without stating a grouping decision was stored as "must be shipped alone", against both the column default and the reception form, where grouping is allowed. Grouping is what the whole trade rests on, so the omission now means allowed.
• Privacy: the personal data export now covers what the eraser deletes. Internal notes on the client record, the internal comment on each parcel and the documents that are not shared with the client were being erased on request but never disclosed on access.
• Fix: refusing an action returned HTTP 500, which reads as a server failure to hosts and monitoring. It now returns 403.
• Fix: the client list printed every page number. It now collapses long ranges and shows the number of records.
• Fix: uninstalling with data removal enabled left the colisly_manage capability on every role and one option behind.

1.6.6

• New: a Settings shortcut on the plugins screen.
• New: a warning on the plugin screens when the store is in coming soon mode or has no payment method enabled, since shipment requests end on the WooCommerce payment page and would otherwise fail with no explanation.
• Fix: adding a client who already has a record announced a creation that did not happen.
• Fix: a pricing tier capped at zero was accepted and silently moved every parcel to the next tier. It is now dropped like an empty row.
• Fix: on narrow screens the parcel dimensions wrapped between a label and its field.
• The allowed carriers help text now states that leaving none checked places no restriction.

1.6.5

• Fix: in the customer area, only the tracking number may now wrap mid-string. In 1.6.4 every cell could, which broke dates and references onto several lines.

1.6.4

• Fix: the pricing tier and carrier fields in the settings overflowed their cells, and the parcel list and the customer tables were clipped, hiding their last column. Long tracking numbers now wrap so the customer tables fit the account column, and wide admin tables scroll instead of being cut.

1.6.3

• Directory listing wording: the tags and the description now use the industry terms "package forwarding", "reshipping" and "consolidation", so operators searching for those find the plugin.

1.6.2

• The installation instructions referred to a "Colis Pro" admin menu, which no longer exists; the menu is "Colisly".

1.6.1

• The plugin and author URLs now point to the plugin directory page and to the author site, instead of a development repository.

1.6.0

• Plugin renamed to "Colisly Parcel Forwarding" (previously "Gestionnaire Colis Pro"), with a matching text domain, to follow the plugin directory naming requirements: a distinctive name rather than a purely descriptive one.
• Internal prefix renamed from "gcp" to "colisly" to meet the four-character minimum required for plugin prefixes. Existing installations are migrated automatically: tables, options, capability, private files directory and WooCommerce order meta are all carried over.
• Fixed URL escaping in the plain-text "shipment requested" e-mail (esc_url instead of esc_url_raw).
• Translation files are no longer bundled: translations are delivered through translate.wordpress.org, and the load_plugin_textdomain() call has been removed (not needed since WordPress 4.6).

1.5.0

• Privacy (GDPR): the plugin now plugs into the native WordPress privacy tools. The personal data exporter includes the client record, parcels, shipments and documents; the eraser deletes documents and private files, blanks phone number, notes, tracking numbers and reception photos, and reports that parcel/shipment records are retained as accounting records. Deleting a WordPress user account removes all of their plugin data and private files.

1.4.0

• Internationalization: all source strings are now in English; the full French translation ships with the plugin (fr_FR .po/.mo), so French sites keep the exact same interface. Translation contexts preserve French grammatical agreement on statuses.
• The My Account endpoint slugs are now translatable and filterable (French sites keep mes-colis, mes-expeditions, mes-documents, demande-expedition; other languages get my-parcels, my-shipments, my-documents, shipment-request by default).
• International default carriers (DHL, UPS, FedEx, Colissimo) on fresh installs.
• New setting to apply the shop taxes to shipment orders (tax-free by default).
• Client search pagination now runs in SQL (COUNT + LIMIT/OFFSET) and scales to large client bases.
• The live estimate on the shipment request form follows the browser locale for number formatting.

1.3.1

• The readme is now written in English, as required by the WordPress.org plugin directory.
• Development files are no longer shipped inside the plugin folder.

1.3.0

• Carrier tariffs (base price + price per kg) configurable in the settings; transport is billed on the native shipping line of the WooCommerce order and included in the shipment total.
• Shipment request: each carrier shows its tariff, incompatible carriers are disabled, and a live total estimate (parcels + storage + transport) is displayed during selection.
• Native WooCommerce e-mails: "Parcel received" (customer) and "Shipment requested" (staff, configurable recipients) registered under WooCommerce → Settings → Emails, with HTML/plain templates that can be overridden from the theme; wp_mail fallback without WooCommerce.

1.2.0

• Native WooCommerce payments: each shipment request creates a WooCommerce order (one fee line per parcel, storage fees, carrier as shipping line); the customer is redirected to the standard payment page and a WooCommerce customer invoice e-mail (with payment link) can be sent automatically.
• Two-way status synchronization: order paid → shipment paid; shipment shipped → order completed; order cancelled → shipment cancelled and parcels returned to stock.
• Client record: the "Order" column links each shipment to its WooCommerce order; the customer area shows a "Pay" button while the order awaits payment.

1.1.0

• Security: client documents and reception photos are now stored in a private directory (.htaccess + random names) and served through an authenticated download endpoint with ownership checks (nonce + capability). Restricted file types (images, PDF, Office).
• Fix: weights and dimensions typed with a decimal comma ("2,5") are now interpreted correctly.

1.0.0

• Initial release: client management (CL references), parcel creation (COL references), automatic weight-based pricing, automatic storage fees, grouping rules, carrier restrictions, shipment requests, documents, history and e-mail notifications.