Delivery Options

Choose a delivery speed and fulfillment method with date promise, price, address eligibility, pickup options, and delivery instructions. This example brings Delivery and Pickup together so shoppers can find the next task without losing context.

It includes representative records such as Standard delivery · Sep 18 and Express delivery · Sep 17. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Delivery Options
Use this template in Figr

Template facts

Screen

Form

Primary action

Use delivery option

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Finance and operations teams need to use delivery option while keeping standard, express and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Delivery gives users an obvious place to start.
  • Supporting view: Pickup keeps the related context close.
  • Primary action: Use delivery option stays visible when people need it.
  • First signal: Standard shows a useful value (Free).
  • Second signal: Express gives additional context (12).
  • Sample record: Standard delivery · Sep 18.
  • Next record: Express delivery · Sep 17.

States worth designing

  • Required field missing: say what changed, protect progress, and offer a clear next step.
  • Invalid value or incompatible data: say what changed, protect progress, and offer a clear next step.
  • Draft saved: say what changed, protect progress, and offer a clear next step.
  • Submitted for review: say what changed, protect progress, and offer a clear next step.
  • No permission to submit: say what changed, protect progress, and offer a clear next step.
  • Temporary save failure: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Delivery → Pickup → Use delivery option → Review outcome

Patterns used

Form, Delivery, Pickup, contextual actions, error recovery

Why these choices work

Show requirements beside fields and retain values after failed checks. Validate only the affected input and make the next step unmistakable.

Pay attention to delivery and pickup. People need to distinguish Standard delivery · Sep 18 from Express delivery · Sep 17. Keep standard visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Use delivery option”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Address Book, Order Tracking, Wishlist.

Start from this in Figr

Design a delivery options screen inside our existing product. Use our current components, tokens and content language. Include Delivery and Pickup views, credible records like Standard delivery · Sep 18, and a clear “Use delivery option” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr