Difference between revisions of "Business process"
From DarkWiki
(→Detailed processes and variations) |
(→Flow (standard)) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
From this point on, things are pretty much automatic. Tracking is received from the carrier, and orders and parcels have their relevant statuses updated as necessary. | From this point on, things are pretty much automatic. Tracking is received from the carrier, and orders and parcels have their relevant statuses updated as necessary. | ||
| − | ==Detailed processes and variations== | + | ==Detailed processes and variations (shipping)== |
===Create orders=== | ===Create orders=== | ||
| Line 30: | Line 30: | ||
* Carrier may be assigned automatically | * Carrier may be assigned automatically | ||
* Only works on allocated parcels | * Only works on allocated parcels | ||
| + | * Must include warehouse identifier (to create labels for the right legs) | ||
* Can include allocation filter/requirements | * Can include allocation filter/requirements | ||
* May also include route assignment (ship via) | * May also include route assignment (ship via) | ||
| Line 44: | Line 45: | ||
* Create parcel and label at the same time | * Create parcel and label at the same time | ||
* Create order, parcels and labels at the same time | * Create order, parcels and labels at the same time | ||
| + | |||
| + | ==Customer flow (standard)== | ||
| + | |||
| + | * Customer places order | ||
| + | * Customer chooses class-of-service | ||
| + | ** Standard delivery, next-day, same-day, Saturday, evening etc. | ||
| + | ** Delivery dates | ||
| + | ** Alternate delivery points (lockers, shops etc.) | ||
| + | * Retailer feeds order to Rabora (including class-of-service data) | ||
| + | * Shipper (if different from the retailer) is notified | ||
| + | * Shipper picks & packs | ||
| + | * Shipper creates parcels, and labels them | ||
| + | * Shipper despatches parcels | ||
| + | * Carrier provides tracking | ||
| + | * Status messages sent to customer | ||
Latest revision as of 08:58, 16 June 2017
Contents
Basic process
- Create order
- Create parcel for order
- Create label for parcel
- Create & send manifest
From this point on, things are pretty much automatic. Tracking is received from the carrier, and orders and parcels have their relevant statuses updated as necessary.
Detailed processes and variations (shipping)
Create orders
- Upload the order details
- Include carrier allocation filter/requirements
- May also include creation of parcels
- May also include route assignment (ship via)
Create parcels
- Create parcels for an existing order (order items should be included)
- Create parcels without an order
- Carrier may be assigned automatically
- Can include allocation filter/requirements
- May also include route assignment (ship via)
Create labels
- Carrier may be assigned automatically
- Only works on allocated parcels
- Must include warehouse identifier (to create labels for the right legs)
- Can include allocation filter/requirements
- May also include route assignment (ship via)
Create manifests
- By default, only parcels despatching today will be manifested
- Future manifests (notifications) can occur if configured
- Can include partially printed consignments
- Partially printed consignments could be split (unprinted allocated parcels are re-allocated to a new consignment)
Additional & compound processes
- Create parcel and label at the same time
- Create order, parcels and labels at the same time
Customer flow (standard)
- Customer places order
- Customer chooses class-of-service
- Standard delivery, next-day, same-day, Saturday, evening etc.
- Delivery dates
- Alternate delivery points (lockers, shops etc.)
- Retailer feeds order to Rabora (including class-of-service data)
- Shipper (if different from the retailer) is notified
- Shipper picks & packs
- Shipper creates parcels, and labels them
- Shipper despatches parcels
- Carrier provides tracking
- Status messages sent to customer
