For ecommerce shipping in Saudi Arabia, choose a carrier by testing your parcel types, delivery areas, returns process and store integration against a written quote. Compare the cost of the complete order, including applicable collection and failed-delivery charges. Before signing, give operations and finance the same test order and ask them to trace it through delivery or return.
Start with an ordinary order from your own catalogue. Pack the item, record the parcel dimensions and choose a destination you expect to serve. You now have something specific to discuss with a carrier. A general promise to deliver across the Kingdom leaves too many questions about your products, collection address and customer experience unanswered.
Create a shipping brief with your collection locations, destination areas, packed weights and dimensions. Include the products that need special handling, your expected dispatch pattern and whether customers will pay online or on receipt. Use measured parcel information and label sales forecasts as planning assumptions.
Separate the moment your warehouse finishes packing from the moment the carrier accepts the shipment. Record your team's dispatch cut-off and request the carrier's collection arrangements in writing. Ask what happens to orders packed after collection and who tells customers about a missed handover. This gives you a basis for the delivery wording at checkout.
Choose representative cases: a routine parcel, a bulky parcel, an address outside your main city and a return. Add cross-border orders only if you plan to sell internationally. Use the same cases with each candidate so a quote for one convenient route does not become your assumed cost for the whole store.
If the platform decision remains open, review our platform choices for shipping workflows. Keep the platform name and integration requirements in the shipping brief; your carrier selection and your developer's scope need to refer to the same proposed setup.
Use the providers' published descriptions to prepare questions for a shortlist. As of October 2026, the following official pages describe these capabilities. Confirm the service, account eligibility and route in your proposal before treating any feature as available to your store.
| Provider | Official description to investigate | Confirmation to request |
|---|---|---|
| SPL | Doorstep, locker and postal-office delivery; reverse logistics; API integration | Which delivery channels and return workflow apply to our destinations? |
| NAQEL Express | Domestic ecommerce delivery with payment on delivery, tracking and SMS notifications; e-fulfilment | Which collection, payment and fulfilment services does our agreement include? |
| FedEx | Ecommerce shipping, tracking, rating and returns integration through its tools and APIs | Which integration and shipping services support our proposed routes? |
Read SPL's ecommerce service description, NAQEL's ecommerce service overview and FedEx's Saudi ecommerce integration options for the source material. These examples help structure a comparison; they do not rank carriers or establish a delivery commitment for your account.
Keep a separate column for evidence. A salesperson's written confirmation, an account-specific service schedule and a demonstrated integration answer different questions. Record the date and responsible contact beside each. Leave unresolved coverage or product restrictions visible until the provider answers them.
Ask every provider to price the same packed parcels and destinations. Request the calculation basis as well as the amount: weight rules, included services, applicable surcharges and billing conditions. Avoid copying a promotional price into your forecast without its qualifying conditions.
| Cost or condition | Question for the written quote | Information your team supplies |
|---|---|---|
| Outbound shipment | How do you calculate the billable weight and destination charge? | Packed measurements and destination areas |
| Collection | Does collection have a charge, minimum or schedule condition? | Collection address and dispatch pattern |
| Extra charges | Which location, handling or fuel charges can apply? | Parcel types and proposed routes |
| Payment on delivery | What are the collection charges and remittance conditions? | Payment methods and reconciliation needs |
| Failed delivery and returns | What do another attempt, return and return collection cost? | Your approved exception and return process |
| Integration and support | Who bills for setup, connector access and maintenance? | Platform, proposed integration and support owner |
Build a worksheet by order outcome. For a delivered prepaid order, add the confirmed outbound and applicable handling charges. For a returned order, include the confirmed return-related charges as well. Keep unknown fields marked “awaiting quote”; your team cannot compare complete costs while treating unanswered questions as zero.
Calculate a planning total using your expected counts for each outcome, then replace those assumptions with actual invoices and order records after launch. Ask finance to confirm the tax treatment and any credits in the supplier documents. This article gives no carrier rate card or universal cheapest-provider claim.
Keep the shipping forecast separate from design, platform subscriptions and development. Our budget checklist for building and running a store covers those wider costs. A developer's integration quote should specify the work and exclusions without implying that carrier bills are included.
Choose by the responsibilities you want your team and supplier to own. Compare a direct carrier arrangement with any proposed shipping platform using the same acceptance checklist. Ask who issues labels, provides tracking, invoices you, handles claims and controls access to historical shipment records.
For a platform arrangement, identify the contracting party for each service. Ask where staff raise a delivery exception and who can correct an address or cancel a label. Request the supported carriers and features for the specific plan and store integration. Do not assume that a carrier logo confirms access to every service that carrier sells.
For fulfilment, write down which warehouse tasks you want to buy: receiving stock, storage, picking, packing and handling returned items. Ask the supplier to quote those tasks separately from transport. Include an inventory discrepancy and a damaged return in the demonstration so your team can see how staff record and resolve them.
Use a practical decision rule: keep packing in-house if you want to operate it and can assign staff to it; investigate fulfilment if you want a supplier to perform the agreed warehouse tasks. Base the decision on a comparable scope and a trial your team can observe. Avoid approving a service category whose daily owner remains unnamed.
Require a complete order demonstration in the supported test environment. Your operator should create the shipment, inspect the label, find its tracking reference and understand the final status using the tools they will have after handover. Request the connector name, version and maintenance owner in the proposal.
Define the events you need the store to display. Label creation, carrier acceptance, a delivery attempt and confirmed delivery represent different steps in your acceptance plan. Ask the developer to map the provider's actual statuses to those steps and show how an unresolved event appears to staff.
Include a repeated shipment request in testing. Your operator should be able to see whether a label already exists before retrying. Ask the developer to demonstrate recovery when a request times out, and record which reference lets support trace the shipment. Do not resolve an ambiguous result by creating another shipment without checking the first.
Test Arabic and English addresses, long names and phone fields on the intended devices. Agree how staff correct incomplete delivery information before dispatch. Our Salla launch checks for catalogue and checkout provides the broader setup sequence; add these shipping tests to the handover for your selected platform.
Ask finance to match a cash-on-delivery order to the amount collected, the provider's deductions and the remittance record. Request the report fields and payment schedule in writing. Keep delivery confirmation and receipt of funds as separate checks so the team can investigate an unmatched transfer.
For online payments, coordinate the shipping and refund procedure with the payment integration. A returned parcel and an approved refund need their own recorded decisions. Our payment-provider checks for refunds and settlement explains the payment side; use a shared order reference to connect the two workflows.
Define who approves a return, who books collection and who inspects the item on arrival. Ask the warehouse operator to record whether the returned item can go back into stock. Then have support explain the outcome to the customer using the approved policy and the current order record.
Include a failed delivery in the trial. Record the reason, the next permitted action and the person responsible. Check the customer message in both languages. Your team should know whether it is arranging another attempt, requesting information or returning the parcel before it sends a promise to the customer.
Agree expected results with the supplier before the trial. Keep evidence beside each case and identify the person who can approve it. A successful label-printing demonstration alone leaves the collection, delivery and finance work untested.
- Create a shipment for the agreed parcel and inspect its label and reference.
- Correct an incomplete address through the approved process.
- Confirm how staff distinguish label creation from carrier acceptance.
- Investigate a delayed or repeated status update without duplicating the shipment.
- Follow a delivery exception through its next action and customer message.
- Complete a return and record the inspection outcome.
- Match a payment-on-delivery remittance to the order and deductions.
- Export the records your team needs for support and finance.
Finish with a handover exercise: give an operator an unfamiliar test order and ask them to find its state, next action and support contact. Record any step that requires the developer's private knowledge. Add the missing explanation to the operating notes before the team accepts the integration.
Send your platform, parcel examples, collection locations, destination areas and provider shortlist. Attach the written quote conditions and describe your return and payment-on-delivery requirements. For online store shipping integration, we can discuss the store work against that brief and identify the integration questions that still need a provider's answer.
Your takeaway is a shipping brief you can test: define the parcel and route, compare complete quoted costs, then trace the order through delivery, return and finance. Ask the proposal to name the account owner, included tests, maintenance responsibilities and exclusions. To scope the store integration, send your shipping workflow and store details.
