E-commerce store
Catalog, filters, cart, checkout. Integrations with ERP, warehouse, payment gateways, delivery and marketplaces.
Updated
An online store with catalog, filters, cart and checkout, connected to your ERP, warehouse, delivery and marketplaces. For retailers that have outgrown an off-the-shelf store. Timeline: 14 days. Priced after a short brief.
What's included
- Catalog with filters and search
- Cart and checkout with guest purchase
- ERP integration (products, stock, orders)
- Payment gateways: Stripe, PayPal, local options
- Delivery: regional carriers integrated
- Marketplaces: Amazon, Ozon, Wildberries sync
- Loyalty program and promo codes
An online store is more than a site with a cart. It's a connected system: catalog, stock, payments, shipping, marketplaces and analytics. If one link breaks, you lose orders every day until somebody notices. We build stores where the storefront, inventory and logistics work as one, and where a buyer gets from a product page to payment without friction.
Who it's for
- Retailers who have sold offline or only on marketplaces and want a channel of their own.
- Stores that have outgrown a site builder: the catalog is slow and integrations are held together with spreadsheets.
- Brands selling on Amazon, Ozon or Wildberries that need stock and orders to stay in sync across every channel.
How we work
- Brief and analysis. We look at your range, where product data comes from, how the warehouse and shipping work, and which integrations are critical: ERP or accounting system, payment provider, carriers, marketplaces.
- Catalog structure and prototype. Categories, filters, the product page and the path to checkout, agreed before design.
- Design. Storefront, product cards, cart and checkout designed so the buyer understands every step and doesn't give up halfway.
- Build and integrations. Catalog, cart and payments, plus data exchange with your ERP, carriers, payment provider and marketplaces.
- Testing. We run real scenarios: placing an order, paying, calculating shipping, syncing stock.
- Launch and follow-up. We go live, watch the first orders and fix bottlenecks as they show up.
What you get
- A storefront that stays fast on a large catalog, so buyers don't leave because pages hang.
- Filters and search that get a customer to the right product in a couple of clicks.
- A short checkout with guest purchase. Fewer steps, fewer abandoned carts.
- Two-way exchange with your ERP or accounting system: products, prices, stock and orders stay in sync, and nobody keeps two databases by hand.
- Payments through providers your buyers already use (Stripe, PayPal or regional gateways) and shipping cost calculated in the cart.
- Marketplace sync, so stock and orders don't drift apart between your site and the marketplaces.
- Orders processed through a queue with retries. If the ERP is down for an hour or the connection drops, the order still arrives once everything is back.
- Promo codes, a loyalty program and email flows in Mailchimp or Klaviyo when you need them.
Technology
For a small catalog WooCommerce is often enough. Larger catalogs and heavy integrations get a custom backend on PHP or Node.js with PostgreSQL, a dedicated search engine and a CDN for images. Card data never touches your server: payments are tokenized on the provider's side, which keeps PCI DSS scope to a minimum.
Timeline and cost
A working store with a standard set of integrations takes about 14 days. The timeline depends on catalog size, the number and complexity of integrations (ERP and marketplace exchange take the most effort) and how ready product data and photos are. A catalog exported from your accounting system and written shipping and payment rules speed things up. Non-standard logic, incomplete product data and slow approvals on third-party services slow them down. We usually launch the basic storefront first and connect the heavier integrations in later iterations.
Cost is estimated after a short brief. It depends on catalog size, the integrations you need, custom design versus an adapted theme, and the number of languages and currencies. Tell us what the store has to do and we'll come back with a figure within a day.
Example
For example, for a retail shop that has so far sold only offline and on marketplaces, we would build its own site with the catalog pulled from the accounting system, set up payment and shipping calculation in the cart, and link stock with the marketplaces. An item sold on the site is written off automatically, orders from every channel land in one place, and nobody has to reconcile stock or copy orders between systems by hand.
What we need from you
- Products in any form: an ERP export, a spreadsheet, even a PDF price list. Whatever is missing we fill in along the way.
- Shipping and payment terms, and access to payment provider and carrier accounts closer to launch.
- Marketplace seller accounts, if sync is part of the job.
- Your return and refund policy. A store selling to consumers in Russia also needs a public offer and personal data documents; see legal preparation.
A broken store costs more than a broken brochure site: a payment page that fails is lost revenue by the hour. After launch we can take the store on e-commerce support with monitoring and agreed incident response times, while content support keeps the catalog filled and up to date.