Couriq organizes delivery creation and tracking with dimensional parcels and vehicles, orange emphasis and black-white cards. Identifiers continue from home to map details, and quotes connect to payment summaries. As the flow grows, success needs an object: saving a card, paying and creating an order produce different results.
Key takeaways
- Identifiers continue across orders, with states and fees needing consistency.
- Card saving, payment and shipment creation need feedback naming their completed objects.
Home separates new tasks from existing orders
New Delivery and Track Package sit together above Current Shipment with name, identifier, place and date; Recent Shipment lists existing records below. Images identify tasks, while identifiers locate specific orders.
Progress dots, checks and vehicles suggest stages, with textual states needing stable definitions. Different names for one identifier in current and recent areas should identify separate levels or use consistent wording.
JVDS would start with identifiers to check names, start/end points, states and fees across pages. This clarifies operation objects more effectively than repeating orange on every screen.
Creation and tracking also need separate return paths. Someone checking a parcel should not refill an order after seeing creation, and starting a new task should explicitly leave the current order unaffected.
Quotes, card saving and payment need separate confirmation
Quotes list Regular, Cargo, Scooter and Cargo Ship with duration and price, using selected borders. Order Summary then divides fees, payment methods have radio selection and adding cards uses a separate form.
Carry the delivery method into the summary, with fee names and total defining payment scope. A new method establishes a condition: after saving, return to the original summary and separately confirm amount and payment.
The success card says Payment Card Added Successful but offers Download PDF and Track your Order. Its title concerns a saved card while actions concern order records. Explain this relationship first; if payment has not occurred, feedback should return to payment choice.
Provide receipts after a clear payment result, retaining identifier and amount. Flow lines make presentation continuous, while actual stages still need names rather than one check image representing every completion.
Tracking retains identifiers and checks costs
Location Tracking shows a route above a dark card with Booking Id, state, date, two places, fee, quantity and weight. Calls and messages connect to the delivery person below. Maps show location while details explain orders.
If costs differ from payment summaries or receipts, identify the difference. Order Cost 120.00 cannot automatically share the definition of other totals; align labels and fee breakdowns.
Maps also need location update time and positioning state. Distinguish completed stages, in transit and expected arrival, linking contacts to the current identifier to retain the inquiry object.
The source field says Form and needs wording suited to an origin. Small copy issues affect understanding alongside states and amounts; correcting them together keeps orders traceable from creation to tracking.
Frequently asked questions
Can saving a card be described as order success?
Describe them separately. Card saving is a payment condition; payment and order creation need their own states, with subsequent entries matching completed results.
Why does tracking need cost definitions?
Different amounts need explained differences when compared with payment and receipts. Name totals, shipping and other fees clearly.
Design review checklist
- Cross-check fields and states for the same identifier.
- Make success feedback concern only completed steps.
- Clarify map time, cost and origin fields.
Align delivery creation and tracking states
Delivery products can organize quotes, methods, payments and creation before connecting identifiers, maps and contacts.
JVDS provides UI/UX design and website design and development. We can work through page content, interface structure and implementation needs together.
