OpenCart
A standalone online store platform. For it we have modules for card payments and electronic receipts, and our own search module, Forge Search. Our OpenCart stores also work with Econt, myPOS and installment purchases through TBI Bank.
Let's talk We choose the technology to fit the project: how many products the store has, which systems it has to connect to and who will maintain it after launch.
We build and support online stores on the following platforms.
A standalone online store platform. For it we have modules for card payments and electronic receipts, and our own search module, Forge Search. Our OpenCart stores also work with Econt, myPOS and installment purchases through TBI Bank.
A standalone online store platform with built-in support for several languages and currencies.
A platform for large catalogs, several warehouses and B2B sales with different prices for different customers.
A store on WordPress, for when the site and the store are managed from one place. For it we have developed modules for shipping, card payments and electronic receipts. Our stores also work with BOX NOW, Pigeon Express, myPOS, Stripe and installment purchases through TBI Bank and iute.
A content management system for sites with many pages and roles. The store is built with the Drupal Commerce module.
A content management system. The store is built with an extension, for example VirtueMart.
Stores, publications and systems, when the process does not fit a ready platform. The publication musicadviser.co.uk and this site run on Laravel.
Stores and B2B systems with many integrations that will be developed for years.
Interfaces with a lot of data and actions on one screen: admin panels, reporting dashboards, product configurators.
Sites and stores whose pages are generated on the server, so they load fast and get indexed by Google. A Next.js storefront can take its data from a Laravel API.
Interfaces that can be embedded in an existing site one part at a time.
Vue sites with server-side rendering of the pages.
Google's framework for large business applications with many forms and user roles.
JavaScript with types. With it, errors in larger projects show up while the code is being written, before release.
Styling of interfaces with ready-made classes, so that all screens look the same.
Removes the background of an uploaded photo right in the customer's browser, with a model that runs on ONNX Runtime Web.
JavaScript on the server: APIs, real-time notifications, integrations and tasks that run in the background.
Databases for stores, catalogs and internal systems.
Cache and job queues, when the site has to respond fast with many visitors. In WordPress and WooCommerce we run it as an object cache with Object Cache Pro.
The same environment for development, testing and the server.
Connections between the store, the warehouse, accounting, ERP and CRM systems. We document the APIs in OpenAPI 3.1.
Our hosting: shared hosting with DirectAdmin, hosting for WordPress and online stores, VPS and Cloud VPS with real-time replication.
The web server of our hosting. In WordPress we add LiteSpeed Cache to it, which serves ready pages from the server cache.
We work with all page builders for WordPress, most often with Gutenberg, the built-in WordPress editor. The client changes texts and photos on their own.
Ready-made store themes: Journal 3 for OpenCart and WoodMart for WooCommerce. Our changes go in a child theme and stay when the parent theme is updated.
Versions of the site in several languages with separate URLs for each language, including stores for several countries in one WordPress installation.
Titles and descriptions for Google, a sitemap, schema.org markup and redirects when URLs change.
Search that shows products while the customer is still typing: iSearch and our Forge Search module in OpenCart. The filters in WooCommerce are built with Filter Everything PRO.
Images are served in WebP format and in several sizes depending on where they appear: thumbnail, card in the product list, main image. In WordPress we convert them with Converter for Media.
We send the store's events to Google Analytics 4: product view, add to cart, order. In WordPress this is done with PixelYourSite Pro, and in OpenCart and in Laravel and Symfony applications through Google Tag Manager.
Conversions and remarketing for Google ads, including enhanced conversions.
The Facebook and Instagram pixel in the browser and the Conversions API, through which orders reach Meta from the server.
Tracking of visits and orders from TikTok ads, from the browser and from the server.
The pixel OpenAI uses to track conversions from ads in ChatGPT.
The banner blocks the advertising and analytics scripts until the visitor accepts them, and the visitor's choice reaches Google through Consent Mode.
We connect the store to an email platform and send it events from the site, for example a started checkout. We also work with Mailchimp, MailerLite and Brevo.
We add interfaces to stores and sites through which an AI assistant searches products and articles and works with the cart.
Actions that an AI agent in the browser can call on the page: product search, reading the page, adding to the cart. We add it to OpenCart and WooCommerce stores.
A server through which an AI assistant searches the store catalog or the site's articles. On musicadviser.co.uk it searches over 11,000 articles.
Files from which the agent learns what the site has and how to use it: llms.txt, an API catalog at /.well-known/api-catalog and an OpenAPI description.
Protocols through which an AI agent searches products in the store and reads their data.