CarryBee courier with SORS ERP
CarryBee is set up as a courier with manual consignment entry, reconciled through statement upload.
CarryBee is one of the couriers Bangladeshi online sellers use alongside the larger names, often for particular routes or rates.
The practical reason to record even a low volume courier properly is that its parcels carry cash. A courier left off the system is a set of receivables with no owner.
What is actually built
Stated plainly, including the parts that are not finished.
CarryBee is configured as a courier in SORS ERP with consignments entered by hand against the shipment, and cash on delivery reconciled by uploading the settlement statement. There is no API integration with CarryBee today; that is on the roadmap.
How to set it up
In order. Each step assumes the one before it.
-
Add CarryBee as a courier
Configure it with shipping classes and the warehouses it serves.
-
Create the shipment against the order
So the parcel is linked to the order and its cash on delivery amount.
-
Record the consignment number
Enter it against the shipment after booking in the courier panel.
-
Upload the settlement statement
Reconcile the covered consignments and post the payout to accounts.
Questions
Answered plainly, including where the answer is no.
Why is only Steadfast API integrated?
Because that is the one that is built. Adding a courier API properly means booking, tracking and settlement handling, and we would rather ship one that works than four that half do. The others are on the roadmap.
Does manual entry mean double work?
It means entering the consignment number after booking in the courier panel. The shipment, the order link and the reconciliation are all in the ERP; what is manual is the booking step itself.
See SORS ERP running on your own numbers
A 30-minute demo in Bangla or English, with your products, your VAT setup and your questions.