28 lines
1.3 KiB
Markdown
28 lines
1.3 KiB
Markdown
---
|
|
question: What is a district, and what happens when a partner is onboarded in a new one?
|
|
also:
|
|
- applocationid
|
|
- region not in the list
|
|
- riders not showing in a new city
|
|
- can I add a district
|
|
area: platform
|
|
source: repositories/partnerRepository.go
|
|
---
|
|
A district is the delivery region a partner works and a rider is placed in. It
|
|
is not the same thing as a branch: a merchant has branches, a district covers
|
|
whichever of them sit inside it.
|
|
|
|
Onboarding a partner into a district that is not open yet **opens it**. The
|
|
district is created along with the operating defaults every rider query needs,
|
|
copied from a district already running rather than invented. So a partner can be
|
|
set up in a city Nearle has not traded in before, without a separate step.
|
|
|
|
This matters because a district that exists in name but has no operating
|
|
configuration hides every rider placed in it. Riders can be created, they appear
|
|
to save, and they are absent from every assign screen. The onboarding path
|
|
creates both halves together so that state cannot be reached from the console.
|
|
|
|
A partner works one district. If a partner's riders are not appearing for a
|
|
merchant, check that the merchant's branches are in the same district as the
|
|
partner, before looking at the riders themselves.
|