# Multiple Carriers Feature

## 1. Scenarios of loads with stops that need to be completed by a single carrier

### A1.
1. create load
2. tender to single carrier
3. remove carrier (carrier docs & invoice removed => status back to Needs Carrire)
4. flow restarts - back to step 2
(we have covered this case)

### A2.
1. create load
2. tender to single carrier
3. add TONU issue for carrier
- carrier will be kept in the jobs list (and flagged as TONU)
- the carrier invoice/financials will only show the TONU issue (to be paid to carrier)
4. assign another carrier, and the following options will be available for broker:
b) remove the carrier
c) mark this carrier also as TONU
- this can be repeated until a carrier that can complete the load is found.
(we have covered this case)

---
## 2. Scenarios of loads with stops that need to be completed by multiple carriers
note: at least 2P/2D & even number of p/d required

### B1.
1. create load with at least 2P and 2D
2. assign 2 carriers for it
3. carriers are ready to complete their part of the load
- both carriers will need to sign the carrier confirmation
- after the first carrier signs the SCC, the carrier will be able to log check calls for its Picks/Drops
- after the first carrier completes the picks/drops, he will upload the POD and his job will be set as Completed
- at this point, the first carrier is marked as completed, his invoice is marked as final, and broker can pay the carrier;
- automatically, the second is set as the active job
- the second carrier will need to sign the SCC, and start logging check calls + upload POD.
- after both carriers carriers have uploaded their POD, the loadStatus is changed to Pod Received & truckStatus to Pod Approved
(we have covered this case)

### B2 (none covered yet)
- create load with at least 2P and 2D
- assign 2 carriers for it
##### B2.1 Mark first carrier as TONU
- we will keep carrier invoice & docs, and mark job as TONU
- we need to be able to assign another carrier on behalf of the first carrier, with the same order and picks/drops

##### B2.2 Remove first carrier
- we should only allow to reassign another carrier, rather than removing it
(since it will set job to null & broke the load's flow)
- issue that might arrise (per Matan): broker might not have a carrier to whom to tender it right away

##### B2.3 Mark second carrier as TONU
- we will keep carrier invoice & docs, and mark job as TONU
- we need to be able to assign another carrier on behalf of the second carrier, with the same order and picks/drops

##### B2.4 Remove second carrier
- we will remove carrier invoice, docs & the job itself
- we need to be able to assign another carrier on behalf of the second carrier, with the same order and picks/drops