
內容簡介
Colisly Parcel Forwarding 是一款專為包裹轉運業務設計的完整客戶及包裹管理系統,適用於使用 WooCommerce 的轉運商、重新寄送商及虛擬地址服務。此外掛提供包裹接收、儲存、整合及重新寄送的功能,並支援多語言翻譯。
【主要功能】
• 客戶管理模組,集中管理客戶資訊
• 包裹創建模組,自動生成唯一包裹編號
• 自動計算儲存費用及包裹狀態
• 客戶端僅顯示相關包裹資訊
• 支援多種運輸公司及自定義設定
外掛標籤
開發者團隊
原文外掛簡介
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.
