Use cases

A store selling across Egypt governorates with different shipping prices

An Egyptian store ships to Cairo, Giza, Alexandria and other governorates with different prices, and wants the price calculated automatically from the customer address at checkout.

Egypt is not one market in shipping: delivery inside Cairo differs from Alexandria, and Upper Egypt shipping carries a wholly different cost. Flat shipping pricing is a double injustice: it overcharges the nearby shopper who pays beyond cost, and eats the margin on far orders costing more than paid. Destination-based pricing solves both together: each shopper pays the true cost of the area, and the store keeps its margin across all governorates.

The merchant defines shipping zones and prices from the Shipping Prices tab at the shipping page: one zone per destination with its price and delivery days, plus a default price for uncovered destinations. At checkout Vareons calculates the total on the server for the destination in order: city, then country, then governorate, then the default price, without trusting any browser-sent value.

In practice, start with the highest-demand areas: Cairo, Giza, and Alexandria with competitive prices that encourage buying, then cover remaining governorates with prices reflecting true cost. Write the expected delivery time per zone clearly to cut where-is-my-shipment questions. Test checkout with different addresses to confirm the right price per destination before announcing.

Among the limits worth knowing, shipping prices follow the carrier own selling rates, which Vareons does not set. Any new area needs a row with its price before it calculates correctly, otherwise the default price applies, which may not cover the cost.

Mapped capabilities

Frequently Asked Questions

How do I add different shipping prices per governorate?

Open the Shipping Prices tab on the shipping page and add a zone per destination with its price and delivery days, keep the default price for uncovered destinations, then test checkout with different addresses to confirm correct calculation.

What happens for an address in a zone I did not cover?

The default price applies automatically to any uncovered destination, so keep the default conservative enough to cover the highest expected cost, and add rows for new areas as soon as orders start coming from them.

Can a shopper manipulate the shipping price from the browser?

No, calculation runs on the server from the merchant table per order destination in the approved order, with no trust in browser-sent values, so the price shown to shoppers is exactly what is computed when the order is created.

Related use cases

Last verified: 2026-09-18

تواصل معنا على واتساب