Keep customer access distinct from merchant login
The current My Orders page uses the email supplied at checkout and a six-digit OTP. It is not the merchant administration account. This distinction gives customers a relevant access route without asking them to understand your internal order-management tools.
Make the entry instructions clear
The page asks for the same checkout email and uses a non-specific message when a code is requested. That message is not a public confirmation that an email has orders. Customers should check their own inbox and use the code privately; support should never request that OTP.
Support a returning customer safely
An authorised session can load the order list, and an expired session returns the customer to the access step. Logout clears the customer session and visible orders. A remembered email suggestion is not itself an authenticated account. On shared devices, encourage customers to sign out after viewing private information.
Set realistic expectations
The value is a clearer route to existing orders, not a promise of a universal account across every merchant or a replacement for customer service. Evaluate the list and status meanings with an authorised example. If an order used the wrong email, resolve it through the merchant's legitimate process rather than trying unrelated addresses.
UNDERSTANDING THE WORKFLOW
Order lookup and customer order history solve different problems
A buyer trying to locate one order has a different task from a buyer reviewing their purchases with a store. Keeping those tasks distinct helps avoid confusing access instructions.
The inspected distinction The order-tracking page asks for an order number and an email or phone number. The separate My Orders page uses the checkout email and a one-time-code flow before displaying the customer’s orders. These are source observations, not proof of a completed live authentication test.
Use the single-order route when the buyer has the relevant reference and needs that order’s status. Use the account-style history route for the supported collection of orders associated with the checkout identity.
Do not request more data than needed Customer support should guide the buyer toward the appropriate interface rather than asking them to send OTPs or unnecessary personal details in a public message. A code is for the authentication flow, not a support quotation.
Keep expectations precise This is not a promise of cross-store purchase history or recovery of orders under every different email address. The owning customer-history feature page should describe the supported scope, while the help articles provide the exact steps and troubleshooting.
Bring this checklist to your evaluation
- Checkout email explained
- OTP kept private
- Correct store accessed
- Shared-device sign-out understood
Check the workflow that matters to your business
Read the relevant setup and troubleshooting guide, then explore getting started with oBizee. Confirm current account availability and terms before committing.