Storefront
Storefronts
Catalogue, product pages, search and checkout, designed for mobile first and in your languages.
- Mobile-first checkout
- HE · AR · EN, right-to-left and left-to-right
Online stores connected to the rest of your business.
Storefronts in Hebrew, Arabic or English, on an established e-commerce platform or a custom build, connected to stock, payments, your ERP and delivery, so an online order reaches the warehouse without anyone typing it in again.
- Payments
- Stock sync
- ERP
- Courier APIs
- HE · AR · EN
What we build
The store, and everything behind it.
The storefront is half the job. The other half keeps orders, stock and invoices in sync.
- Storefront
Storefronts
Catalogue, product pages, search and checkout, designed for mobile first and in your languages.
- Mobile-first checkout
- HE · AR · EN, right-to-left and left-to-right
- Stock
Stock sync
Stock levels read from your ERP or warehouse, so the site shows what you actually have.
- Read from the ERP or warehouse
- One source of truth per field
- Payments
Payments
Card payments and installments through the payment provider you already work with.
- Cards and installments
- Your existing provider
- ERP
ERP and accounting
Orders, customers and invoices sent to your ERP or accounting system.
- Orders and invoices sent automatically
- Customers kept in sync
- Shipping
Shipping
Delivery options, labels and tracking updates connected to your courier's API.
- Labels from the courier's API
- Tracking updates to the customer
- Migration
Store migrations
Moving from another platform with products, customers, orders and URLs carried over.
- Products, customers and orders
- Old URLs redirected
01 / 06 · swipe
After checkout
An order is done when the warehouse has it.
We plan the flows behind the store as carefully as the pages in front of it. Every order moves through payment, stock, the ERP and shipping without anyone typing it in again.
Failed syncs are retried
A failed run is logged and retried, repeated failures raise an alert, and orders wait in a queue instead of being lost.
One source per field
We decide with you which system owns stock, prices and customers, so the two don't overwrite each other.
Order notifications
Confirmations and tracking updates by email or WhatsApp.
E-commerce tracking
GA4 e-commerce events, so you can see which pages and campaigns sell.
Integrations
The store talks to every system behind it.
Stock and prices come from your ERP, payments from your provider, labels from your courier. Each connection is logged and retried, so a slow system never loses an order.
Behind the store
After the order
ERP
stock · prices · orders
Payments
cards · installments
Accounting
invoices · customers
Your store
Storefront and checkout, with a sync layer that queues and retries every call.
Courier
labels · tracking
Email · WhatsApp
confirmations · updates
Analytics
GA4 e-commerce events
Behind the store
ERP
stock · prices · orders
Payments
cards · installments
Accounting
invoices · customers
Your store
Storefront and checkout, with a sync layer that queues and retries every call.
After the order
Courier
labels · tracking
Email · WhatsApp
confirmations · updates
Analytics
GA4 e-commerce events
How a store project runs
Tested with real orders before the first customer places one.
Each stage ends with something you can check before the next one starts.
- Cataloguetypes · variants · prices
- Integration planwho owns each field
- Stagingthe store on staging
- Test orderspayment → ERP → courier
- Launchcheckout monitored
- Cataloguetypes · variants · prices
- Integration planwho owns each field
- Stagingthe store on staging
- Test orderspayment → ERP → courier
- Launchcheckout monitored
Catalogue
Catalogue and flows
Product types, variants, pricing rules and the path from cart to delivery, agreed with the people who run the store.
Integration
Integration plan
Which system owns stock, prices and customers, and how often each one syncs.
Testing
Build and test orders
The store is built on staging and we place test orders end to end: payment, ERP, shipping and emails.
Launch
Launch and operate
Go-live with monitoring on checkout and sync jobs, then hosting, updates and fixes.
Case study
A store that sells the product and tells its story.
Natural products · HibaVie
An online store for natural olive oil products.
- Store
- A product catalogue and product pages, with cart, customer account and checkout.
- Brand
- Brand pages next to the shop: about, a journal and an FAQ.
- Design
- A design built on the brand's own logo and palette.
FAQ
Questions before a store project.
A ready-made platform or a custom store?
A ready-made e-commerce platform covers most catalogues and gives your team a familiar admin for products and orders. We build custom when the pricing, the catalogue or the order flow does not fit one, or when the store is part of a larger system.
Can the store use stock and prices from our ERP?
Yes, if the ERP exposes them through an API or an export we can schedule. We decide with you which system is the source for each field, so the two don't overwrite each other.
Which payment providers do you work with?
The one you already have an agreement with, as long as it offers an API or a plugin for your platform. If you don't have one yet, we go over the options with you.
Can you move our existing store without losing orders and customers?
We migrate products, customers and order history, and redirect old product and category URLs to the new ones. A test migration runs first so you can check the result.
What happens if the sync with our ERP fails?
We design the sync so a failed run is logged and retried, repeated failures raise an alert, and orders wait in a queue instead of being lost. That way the store can keep selling in the meantime.
Next step
Send us your catalogue and the systems behind it.
Your current store, your ERP and the courier you use. We will come back with an integration plan.