Document Status | IN REVIEW |
---|---|
Closing date | |
Document Owner(s) | |
Reviewers | |
Epic Link | |
Figma Link |
🛠️ Potential Solutions
🧐 Assumptions
Admin Tool does not provide the phone number information provided by the customer during the ordering process.
Customer is not required to register a phone number in their profile.
Customers may provide different numbers for each order.
If the Customer phone number is not provided it will be shown three dashes or points according to the brand design.
✅ Proposed Solution
Get the user's phone number from the customer data and order phone number from the order data.
For more references:
✅ Pros:
Quick implementation.
Proposal
Update FetchOrder query
Add phoneNumber to dropoff and customer
export const FetchOrder = gql` query Order($rbiOrderId: String!) { Order(rbiOrderId: $rbiOrderId) { id: rbiOrderId __typename ... customer { ... phoneNumber } delivery { ... dropoff { ... phoneNumber } ... } } ${CartEntryFragment} `;
Update Dropoff interface
Add
phoneNumber
to the Dropoff inservices/graphql/src/schemas/orders.ts
and runyarn types
.
Add phone number info to the table
Add new translations
loyaltyCartDetails.customerPhoneNumber
: Profile phone number.orderDetails.phoneNumber
: Order phone number.
🎛️ Configuration
No feature flags are needed as this solution does not impact any existing processes and does not significantly change the support tool UI.
🗓️ Delivery Plan
Update query and interface
Add new fields table
Add new Lokalise translations
🧑🚒 QA Plan
Scenario | Condition | Result |
---|---|---|
Profile Phone Number and Order Phone Number populated | Both Profile Phone Number and Order Phone Number should be populated | Both Profile Phone Number and Order Phone Number should have values different ou equal values |
Order Phone Number populated. | Only Order Phone Number should be populated. |
|
Add Comment