Make the catalogue usable
Prepare product names, accurate descriptions, images, prices, stock fields and variants before import. Decide how customers browse by category, size or another useful attribute. Check a representative simple product, a variant product, an unavailable item and a search with no result.
For multilingual stores, agree which product fields and messages need translation and who maintains them. On mobile, verify readable prices, usable options and clear add-to-cart feedback. A visually complete homepage does not establish that the catalogue is ready.
Confirm payment and settlement
Check the actual merchant’s country, legal/business requirements, supported currency and provider eligibility. Agree the account owner, integration method and settlement process with the chosen provider. Gateway and platform fees remain separate from a build price unless the proposal says otherwise.
Test successful, declined, cancelled and duplicate submissions in an authorised test environment. Verify that order status and stock reflect the intended outcome. A success screen alone does not prove that the provider accepted or settled a payment. Do not make live charges simply to test a design without explicit authorisation.
Define delivery and exceptions
Write down delivery areas, charges, order cut-offs, fulfilment responsibility and the information a courier needs. If serving customers outside Lebanon, review the actual shipping, currency and provider requirements for those destinations rather than assuming the local setup applies everywhere.
Decide how the team handles an incorrect address, unavailable product, failed payment and return request. Publish policies that match the actual business and applicable requirements. A copied template is not a substitute for confirming those facts.
Check the complete order journey
Use an authorised test order to inspect cart quantities, discounts, shipping, checkout validation, notifications, stock changes and the staff order view. Check confirmation messages and support routes on a phone as well as a desktop. Agree how order data reaches any external inventory or operational system.
Before changing the live domain, check backups, permissions, HTTPS, redirects from replaced URLs and search indexing directives. Record who can restore the site and who owns launch exceptions. Schedule a post-launch review using real order and enquiry evidence rather than relying on a launch-day screenshot.
Match the build and care scope
IWORQS online stores start at $1,800, with final catalogue, payment, shipping, design and integration scope agreed in the proposal. Hosting, paid platform/tool fees and ongoing services are separate unless included. Current starting prices are available on our pricing page.
Selected commerce presentations include On+, Tech Nails and Obagi Kuwait. Their recorded case scopes describe the work; a portfolio image is not evidence of a particular gateway, conversion increase or live technical stack. After launch, choose a suitable care or management scope for the platform and the amount of product work required.
Make the next decision.
Official references
Provider requirements can change. Check the current documentation for the actual platform and account.
This guide explains our published scope and planning approach. A proposal confirms the work for your business; examples do not establish a client’s technical stack or measured results.