~ 6 min

Qbrick System sells modular tool boxes, organizers and carts across Russia. Their Tilda store ran on foreign Make and Airtable, and managers often copied orders into CDEK and 1C by hand. We moved the logic to self-hosted n8n and SeaTable on a server in Russia and connected CDEK and 1C. Now an order goes to delivery with the right tariff, the tracking number lands in the database, and the sale appears in accounting without manual entry.

Imagine selling modular boxes, organizers and carts for tools. You have four product lines, a showroom, service and spare parts, and customers pay on delivery at a CDEK pickup point. Every order has to be created in CDEK, a tariff chosen, the tracking number sent to the customer and the sale entered into 1C. Done by hand, a manager spends the whole day copying data between systems.

The Qbrick System team (qbsystem.org) came to us with exactly that. We first automated CDEK, and in stage two we moved the whole backend to a self-hosted stack and connected 1C. The client came back to us on their own.

- Foreign Make and Airtable. Paying for subscriptions from Russia is hard, plans have operation limits, and an account block would have stopped the whole store.
- Manual shipping. CDEK orders were first created by hand, and tracking numbers went to customers separately.
- Gap with accounting. Orders from the site had to be moved into 1C separately.
- Address errors. Customers type addresses in different ways, which delays parcels.
- Remote regions by hand. The standard Tilda cart cannot calculate delivery to remote regions, so the sales team entered such orders manually. In practice the store served central Russia only.

- Create a CDEK order automatically after purchase and write the tracking number to the database.
- Move all logic from Make to n8n and the data from Airtable to SeaTable, on our own server in Russia.
- Pick the right CDEK tariff automatically.
- Sync orders with 1C.
- Validate customer addresses and monitor the server.
- Calculate delivery to remote regions at checkout.
- Build a customer account.
- Improve the cart and checkout on Tilda.

Customers see the same Tilda storefront. Everything that happens after “Place order” now runs on n8n and SeaTable on the client’s server at Timeweb. Foreign services are no longer needed, and the data and workflows belong to the store.

Before: the store logic lived on foreign Make and Airtable, with block and payment risks. CDEK orders were initially created manually.

After: all logic runs on n8n and SeaTable on the client’s own servers in Russia. An order goes to CDEK with a suitable tariff, the tracking number lands in the database, and orders sync with 1C. Delivery to any region is calculated automatically, and customers have an account.

Result: the store delivers across the country, including remote regions, and the sales team no longer enters such orders by hand. With the account, 4–5 out of 10 customers come back for a repeat order. The client returned for stage two.

Tilda — storefront, catalog, cart and checkout.

n8n — the store backend instead of Make: order processing, CDEK, 1C, notifications.

SeaTable — orders and products database instead of Airtable, readable to a manager like a regular spreadsheet.

CDEK API — automatic shipment creation, cargo-place split, tariff selection and tracking numbers.

1C — order sync with accounting.

Dadata — address validation and suggestions.

Telegram — server status alerts.

Timeweb + Cloudron — the client’s own server in Russia and convenient service management.

- The backend and data live on the client’s own server in Russia: no dependence on foreign subscriptions and no risk of an account block.
- The new logic was tested before switching, and the store moved without stopping sales.
- Server monitoring with Telegram alerts: the team learns about a problem before customers do.

- Stage two took 10 days (12–22 June 2025).
- The client came back: two stages of work together.
- Delivery across Russia, including remote regions.
- 0 manual remote-region orders for the sales team.
- 4–5 out of 10 customers return for a repeat order.

If your Tilda store relies on manual shipping, foreign subscriptions and copying orders into accounting, describe it in the brief. We will estimate the work and suggest what to remove from manual work first. The backend will run on your server, and all workflows and data stay with you.

We describe the migration itself in a series case study: how we move a business backend without stopping sales.