Ecommerce in Kropyvnytskyi: parts, agri, local products

Ecommerce in Kropyvnytskyi: selling under the specifics of an agri region

Kropyvnytskyi is a city whose economy rests on agribusiness, food processing and machinery production, so ecommerce projects here carry their own logic. This is not «a women's dress shop with a default checkout» but B2B parts portals with 10000 SKUs, export marketplaces for grain traders, niche stores for local agri products (honey, oil, seeds). I work with teams on Velyka Perspektyvna, around Chervona Zirka, in coworkings near Universytetskyi avenue, and I know what a real sales cycle looks like in the field and on export.

B2B parts shops as the main genre

The most common request from machinery dealers in Kropyvnytskyi is to build a B2B shop with 5000-15000 SKUs and real 1C or BAS integration. The dealer logs in, sees their personal discount (by category, volume, region), real-time stock, order history and documents. The order flows into 1C automatically, the Nova Poshta waybill is created from the manager cabinet and the customer receives an SMS with the number. This is not a hand-built shop but an engineered product that saves 40-60 hours of manual manager work per week in peak season.

Agri exports to the EU

A separate strong niche is export stores for cold-pressed oil makers, honey, seeds and craft food. The Ukrainian product in Poland or Germany competes not on price but on quality and certificates — and your store has to show that. I build English + Polish or German versions, EUR payments through Stripe with SEPA for wholesalers, integration with European couriers (DPD, GLS) and automatic customs declarations. The audience is an eco-buyer in Warsaw or a Berlin family looking for Ukrainian sunflower oil.

The technology stack: why Next.js plus Medusa

For new projects I use Next.js (React) with SSR/ISR on the front and Medusa.js or Shopify Plus on the back. Why this stack: Medusa is open-source, headless, with no vendor lock-in and flexible enough to fit Ukrainian realities (Nova Poshta, LiqPay, VAT). Shopify Plus suits export shops where launch speed and global payments matter. I deliberately avoid WooCommerce for serious B2B — it is heavy, slow with 5000+ SKUs and vulnerable. Magento is too expensive and complex for regional budgets.

Integrations you cannot ship without

No Ukrainian ecommerce flies without integrations: 1C/BAS (two-way exchange of products, prices, stock and orders), Nova Poshta (branches, lockers, waybills, tracking), Ukrposhta, payments (LiqPay, Fondy, WayForPay, Monobank, Stripe for export), email (SendPulse, eSputnik), SMS (TurboSMS, Stream Telecom). I configure all this from the start, not «as a separate post-release package». Each integration is tested with real data on staging.

Analytics and conversion optimisation

A shop without analytics is a black box that spins without anyone knowing where the money is. I install GA4 with full ecommerce tracking (15+ events), Google Tag Manager for flexibility, Hotjar for session recordings, Meta and TikTok Pixel for ads, server-side GTM to bypass blockers. A separate Looker Studio dashboard you open once a week. A separate package is conversion optimisation: first a GA4 and Hotjar audit, then 10-20 hypotheses ranked by impact/effort, then A/B tests via VWO. A typical 3-month result moves conversion from 0.8% to 2-3%.

Seasonality as a technical challenge

For agri-ecommerce in Kropyvnytskyi seasonality is the main pain. Before sowing and harvest traffic grows 5-10x in a week and the infrastructure has to absorb that without falling. I use a CDN (Cloudflare), an ISR-cached catalogue, Redis for prices and horizontal scaling for Node.js. On staging there are k6 load tests at 1500+ rps. A separate marketing calendar — content, email and push — ties to the «prep-sowing-vegetation-harvest» cycle. This is a systemic approach, not «let us buy more servers».

How the process runs: from idea to launch

Step one is a 30-minute call or meeting in a cafe on Soborna or Velyka Perspektyvna where I listen to your situation without slides. Then comes paid discovery (5-10 days, 400-800 USD) where I run interviews with the owner, managers, warehouse and logistics team; I draw an audience map, the catalogue structure, the checkout flow and a list of integrations. After discovery you own an artefact with KPIs and a roadmap. If we continue — design (3-4 weeks), development in two-week sprints, training for your team, release. After release a free month of warranty support, then your chosen support package.

Transparency and code ownership

All tasks live in GitHub Projects and you see every ticket 24/7. A weekly 30-minute call with a demo. The code is fully yours — pushed to your GitHub account, with documentation and architecture diagrams. You can move the project to another developer at any moment with no losses. This is a principled stance: I do not hold clients through a «secret stack» or vendor lock-in.

Most common requests from Kropyvnytskyi

Over the past year the top requests have been: B2B parts shops for machinery dealers with 1C integration, export shops for cold-pressed oil to Poland and Germany, niche shops for seeds and fertilisers, dropshipping projects with Turkey and Poland, and local shops for honey and craft food. Separately — optimisation of existing shops that are not converting. If your request is something else — write to me and I will say honestly whether it is in my zone.

Subscriptions for agri products: a new format for the region

The subscription model is when a customer does not buy once but signs up for regular delivery. Globally this is normal for coffee and wine, but in Kirovohrad-oblast agri it is fresh territory. Over the past two years I see growing requests from oil, honey, flour and herbal-tea producers — «set me up with a subscription, the customer gets their batch every month or every quarter». The economics: a subscriber delivers 3-4x higher LTV (lifetime value) than a one-off buyer because you do not spend budget on re-acquiring traffic. One new Polish subscriber on a 12-month oil delivery is 480-720 EUR of guaranteed revenue.

Technical implementation of subscriptions

I build subscriptions through Stripe Subscriptions (for export) or a custom flow on LiqPay recurrent payments (for Ukraine). The customer picks frequency (monthly, every two months, quarterly), batch size and shipping method. Each new cycle automatically charges, generates an order in the admin, books the Nova Poshta or DPD waybill and notifies the warehouse manager. If the customer wants to pause, cancel or change address — a separate self-service cabinet, no manager call needed. This removes 70-80% of routine sales-team work and makes revenue forecastable.

Case: cold-pressed oil on a 14-month subscription

An oil producer near Oleksandriia launches a «1 litre per month» subscription at 18 EUR. Four months after release — 137 active subscribers from Poland and Germany. Monthly revenue from subscriptions alone — 2466 EUR, net profit per subscriber 4-5 EUR/month after logistics and fees. But the main thing is stable cash flow that lets you plan raw material purchases and presses utilisation. This is a separate ecommerce genre that is still under-exploited in Ukraine.

Dealer B2B portals: deeper than «a shop with a password»

Half of my Kropyvnytskyi ecommerce projects are not «a shop for a person» but a closed B2B portal for dealers. A machinery dealer network with 8-15 outlets carries its own logic: each outlet has a credit limit at head office, personal volume discounts, individual delivery terms, a separate document cycle (invoice, dispatch note, waybill, act of acceptance). These processes do not fit a «regular» shop — a separate architecture is needed.

How I build the B2B cabinet

The dealer logs in via email/password or SSO (if you already have corporate authentication). On the home view — their personal dashboard: current balance with head office, credit limit, statuses of active orders, new warehouse arrivals. Catalogue with personal prices (the discount is computed automatically by category and volume), filters by brand, machine model, article. Cart with VAT calculation, payment options (prepay, net-30, staged), delivery options (pickup from Kropyvnytskyi, Nova Poshta to address, branded transport). After checkout — automatic documents, waybill, Telegram or email notifications.

Integration with the accounting system

All of the above is the front end, but without the back side it is dead. I build a two-way sync with 1C/BAS: products, prices, stock, counterparties, documents. Stock refreshes every 15-30 minutes, prices instantly upon change at head office, counterparties are two-way (a new dealer is added in both systems at once). An order from the cabinet automatically lands in 1C as a new document with «new» status; the manager in Kropyvnytskyi sees it and can confirm, reject or adjust. This is a live integration, not a CSV upload at night.

Payment logistics for agribusiness

Regular ecommerce stops at LiqPay and Apple Pay. For agri that is not enough. In my Kropyvnytskyi projects the standard set is wider: LiqPay (retail), Monobank Acquiring (low fees, fast onboarding), Fondy (for legal-entity businesses), Stripe (EU export), Wise Business (SEPA wires for wholesalers), pay-by-invoice (B2B segment, PDF invoice generation, manual confirmation by the accountant after funds arrive), instalments via monobank Parts.

«Pay by invoice» as a separate flow

This is a Ukrainian B2B specific: a farmer-customer does not want to pay by card online for an 80,000 UAH order — they want a PDF invoice, a bank transfer, then delivery. I implement this as a separate payment flow: the customer picks «pay by invoice», the system generates a PDF with all details (including VAT), emails it to the customer and into the manager's CRM. After funds arrive the manager confirms the payment manually — and the order automatically moves to «paid» status, the waybill is generated. This removes the need for voice contact with a manager on every order.

Crypto for export

USDT/USDC over TRC-20 or ERC-20 networks — a separate channel for export orders where SWIFT wires are expensive and slow. I plug crypto acceptance through NowPayments or Coinbase Commerce, with automatic conversion to EUR on your Wise or bank account. A 0.5-1.5% fee versus 30-80 EUR per SWIFT — significant savings. For wholesale agri contracts with Africa or the Middle East this is often the only working option.

Shipping: from Nova Poshta to European couriers

Ukrainian shipping is not «turn on Nova Poshta and ship». It is a separate technical task with 5-7 integrations. In my standard stack: Nova Poshta (branches, lockers, address delivery, waybill generation from the manager cabinet, label printing, status tracking), Ukrposhta (for remote villages without NP), Meest, Justin, branded transport (for heavy goods — machinery, equipment). Separate logic for branch selection: the customer types «Oleksandriia» and the system suggests every branch in the city with type filters (regular, locker, Box).

EU export logistics

For export I configure DPD, GLS, DHL Express, UPS — depending on country and product type. Each integration has its own API format, tariff rules and weight/size restrictions. A separate task — customs declarations: for parcels under 150 EUR only a CN23 is needed, above — a full declaration with a HS code. I automate generating these documents in the system so the Kropyvnytskyi manager does not fill them in by hand for every order.

Cross-border economics

For a Ukrainian oil producer in Oleksandriia who exports to Poland, the real cost of shipping 1 kg in retail format (1-2 bottles per box) is 4-7 EUR through DPD. That is 25-40% of product value and eats margin. I help optimise: bundled shipping (the customer orders in multiples — 6 bottles per box, 8-9 EUR delivery instead of 4×6=24 EUR), a courier contract on volume (-15-25% above 200 parcels per month), warehouse outsourcing in Poland (a partner warehouse in Rzeszów, then EU delivery from there at 2-4 EUR). Not magic — just logistics treated as a separate funnel.

SEO for Ukrainian ecommerce

Ecommerce without SEO is a shop in a back alley with no sign. I bake SEO into the architecture from day one, not «after release». Schema.org structured data — Product, Offer, BreadcrumbList, Organization, FAQ on every product page. URL structure aligned with keyphrases (/parts/for-jcb-tractors/, not /products/?id=4892). Sitemap.xml with priorities, auto-updated on catalogue changes. Robots.txt correctly configured for /admin, /cart, /checkout. Canonical tags to fight duplicates (filters, pagination). Open Graph and Twitter Cards for socials.

Content strategy for an agri catalogue

A separate task is text content. A product card cannot be «JCB 3CX, 12000 USD, in stock». I write extended descriptions: machine type, technical specs, year, hours, warranty, available trims, optional equipment, service history, 8-12 angle photos, video walkaround. Useful for the buyer, useful for Google — it raises time on page and rankings. For a parts catalogue — compatibility instructions, cross-links to similar models, forum-style Q&A.

Local SEO for Kropyvnytskyi

A separate layer is local SEO. «Buy a tractor in Kropyvnytskyi» is a separate query, distinct from «buy a tractor in Ukraine». I configure a Google Business Profile with every branch (Kropyvnytskyi, Oleksandriia, Znamianka, Svitlovodsk), Local Business Schema on contact pages, customer reviews from oblast cities, local landing pages per city («parts in Oleksandriia», «service in Svitlovodsk»). This delivers 40-60% extra organic traffic versus a Ukraine-wide SEO strategy.

Post-launch shop support

A shop is a living system where something happens daily: the 1C integration suddenly stops after a server firmware update, Nova Poshta changes its API and waybills do not generate, in peak season Cloudflare distributes traffic unevenly, GA4 analytics suddenly stops showing transactions. I run an SLA package for critical incidents: 24/7 monitoring (Sentry, UptimeRobot), 4-hour response on critical incidents during business hours, 8 hours on weekends. Weekly — a brief report with metrics: traffic, conversion, AOV, top products, issues. If the Kropyvnytskyi client wants to administer themselves, I train the team and hand over documentation.

Start

If you are still reading — write to contacts, browse cases, or jump into adjacent development or CRM/ERP/SaaS if you need not just a shop but full automation. The sooner we start, the bigger the chance to make the next season.