Skip to main content

Portal Configuration

Customer portal configuration controls customer-facing delivery settings

Portal Configuration controls what customers see and can do in the delivery customer portal. Use it to set pickup address behavior, available services, COD rules, optional delivery fields, package options, tracking visibility, branding, support tickets, wallet payout eligibility, and custom domain connection.

Go to Delivery Management -> Portal Configuration.

Portal Configuration pickup settings

How the page works

Settings are grouped into tabs. Each tab has its own Save button. Changes in one tab are not saved until you click that tab's save button.

If a save button is disabled, Ondi has not detected a change in that tab.

Pickup Settings

Pickup settings control how customers choose pickup addresses in the customer portal.

Allow Change lets customers change the pickup address.

Pickup Mode controls the pickup selection behavior:

  • Fixed Default uses the default pickup address and disables the allowed address list.
  • Select from List lets customers choose from allowed pickup addresses and disables the default pickup address field.
  • Predefined Only uses configured addresses so customers cannot freely choose any address.

Default Pickup Address is the address Ondi uses when the mode requires one default.

Allowed Pickup Addresses is the list customers can choose from when the mode allows a list.

Use the plus icon in address fields to create a new address without leaving the configuration page.

Delivery Services

Delivery service settings control which services customers can use in the customer portal.

Default Delivery Service is the service selected by default when the portal needs a default option.

Allowed Delivery Services limits the delivery services shown to customers. Leave the list broad only when customers should see all active portal-eligible services.

Delivery services themselves are configured in Delivery Services. Portal Configuration decides which of those services are exposed to customers.

COD Settings

COD settings control cash-on-delivery behavior in the customer portal:

  • COD Enabled allows customers to use COD.
  • COD Required makes COD amount mandatory for all customer-created deliveries.
  • Allow Zero Amount allows a COD value of zero.
  • Minimum Amount sets the lowest accepted COD value.
  • Maximum Amount sets the highest accepted COD value. Leave it empty when there is no maximum limit.

Use COD rules carefully. If COD is enabled but not managed operationally, drivers and finance teams can end up with outstanding collections.

Delivery Fields

Delivery field settings control optional fields in customer delivery creation:

  • Reference ID allows customers to enter their own order or reference number.
  • Invoicing enables invoice-related fields.
  • Custom Shipment Label allows customers to add custom shipment-label information.

Enable only the fields customers actually need. Fewer fields make customer order creation faster.

Package Settings

Multipart Packages allows customers to create deliveries with more than one package. Use this when customers commonly send multiple boxes under one delivery.

If multipart packages are disabled, customer-created deliveries stay simpler and are easier to rate and label.

Visibility

Visibility settings control what customers can see while tracking deliveries:

  • Show Driver Info displays driver information on the tracking page.
  • Show Driver Phone displays the driver's phone number.
  • Real-time Tracking enables live delivery tracking where driver location data is available.
  • Support Chat allows customers to use support chat.
  • Driver Chat allows customers to chat directly with the delivery driver.

Use driver phone and driver chat only when your operating model supports direct customer-driver contact.

Brand Settings

Brand settings control the customer portal's visible identity.

Portal brand settings

Brand Name is the customer-facing name. English is required. Arabic and Kurdish can be added when the customer portal needs translated names.

Auto Translate can fill Arabic or Kurdish from the English name when translation support is available.

Page Title controls the browser or page title.

Brand Assets include:

  • Logo: square image, up to 1024 x 1024 pixels, maximum 3 MB.
  • Favicon: 16 x 16 or 32 x 32 image, maximum 3 MB.

Theme Colors control customer portal colors. Use the swatches or edit the color values. Keep contrast readable when changing text, button, or status colors.

Support Ticket Settings

Support ticket settings

Support ticket settings control whether customers can create support tickets from the portal.

  • Enable Support Tickets turns customer portal ticket creation on.
  • Allow Customer Close lets customers close their own tickets.
  • Auto-assign on First Reply assigns the ticket to the support user who replies first.
  • Default Priority sets the initial ticket priority: low, medium, high, or urgent.
  • Support Users selects non-customer users who can receive or handle support tickets.

Disable customer close when every ticket needs staff verification before closure.

Wallet Settings

Wallet settings

Wallet settings control which customer types are allowed to request wallet payouts from the customer portal:

  • Business allows business users to request payouts.
  • Individual allows individual users to request payouts.

These settings affect customer-facing payout requests. Tenant admins can still review payout activity in the Financial Dashboard.

Connect Custom Domain

Use this tab to connect a customer portal domain owned by the tenant.

Custom domain settings

When no domain is connected, enter a domain such as delivery.example.com. Enter only the domain, without http://, https://, or a trailing slash.

After connection, Ondi shows DNS records to add at the DNS provider. DNS changes can take 24 to 48 hours to propagate. Once DNS is ready, use verification to connect the domain.

When a domain is active, the tab shows:

  • connection status
  • live portal URL
  • connection date
  • DNS records
  • copy-record action
  • disconnect action

Disconnect only when customers should no longer use that domain for the delivery portal.

Good practices

Review Portal Configuration after creating or changing Delivery Services, COD workflows, wallet payout policies, or support teams.

Test the customer portal after brand, service, pickup, COD, or custom-domain changes. These settings directly affect what customers see.

Keep customer-facing options simple. Show only the services, fields, and contact options that your team can actually support.

Ask Ondi AI