Alexander Koltsov —
ERP and Operations Consultant

Each channel used its own product, order, and customer structures. Maintaining consistent SKUs, stock positions, payment data, fulfillment status, and accounting records across marketplaces required repeated reconciliation and created a risk of fragmented operational data.

Alexander designed the Odoo-centered integration architecture and end-to-end data flows for products, variants, orders, customers, payments, inventory, fulfillment, invoices, and accounting. He addressed the mapping of shared SKU and variant identities where external platforms used different attribute and value models.

Reduced reliance on repeated cross-channel data handling, improved inventory and order visibility, lowered reconciliation risk, and created a basis for adding sales channels without proportionally increasing manual back-office work.

Product variants, orders, customers, inventory, and fulfillment had to remain synchronized between the storefront and the operational system at a scale where inconsistent identifiers or manual updates could quickly affect order handling and stock reliability.

Alexander worked on the Shopify Plus–Odoo architecture and synchronization scope, covering product templates, variants, SKUs, customers, orders, stock, and fulfillment. He translated commerce requirements into ERP processes and integration rules suitable for a large catalogue and recurring order volume.

Reduced duplicate handling between commerce and ERP systems, improved the consistency of catalogue and inventory data, supported dependable fulfillment, and created an operational foundation for growth in order volume and product range.

Procurement, raw-material storage, recipes, unit-of-measure transformations, production stages, finished goods, replenishment, fulfillment, and accounting needed to be represented as one coherent process. In some scenarios, lots, expiry dates, FEFO, landed costs, and international procurement added further control requirements.

Alexander analysed and designed end-to-end Odoo flows covering bills of materials, manufacturing orders, work centres and operations, MTO and MTS rules, procurement, replenishment, consumption, finished goods, multi-warehouse inventory, lots, expiration dates, FEFO, valuation, landed costs, marketplace demand, fulfillment, invoicing, and accounting. For tea production, the scope included kilogram-to-sachet conversion, mixing, packing, fermentation, crushing, recipes, and production consumables.

Made production flows more transparent and reproducible, reduced reliance on informal coordination, improved stock and cost traceability, and created a structured basis for planning, control, and scalable manufacturing execution.

Warehouse activity and 3PL services had to be translated into controlled operational events and billable services. Without a unified model, fulfillment execution, client-specific charging, and supporting data could remain dependent on manual interpretation and reconciliation.

Alexander analysed the fulfillment model and designed the ERP processes linking warehouse operations, logistics events, integrations, and billing. He developed the process logic for interaction with 3PL operations and for converting performed services into structured billing data.

Reduced dependence on manually reconstructed billing, improved the traceability of chargeable operations, increased control over fulfillment workflows, and created a foundation for serving more clients without proportional growth in administrative effort.

Data access and interpretation were separated: users had to locate figures, reconcile sources, prepare reports, and then investigate drivers of changes. A generic AI assistant could not safely be treated as a source of financial truth.

Alexander developed a controlled reporting architecture in which AI uses authorised tools and Model Context Protocol connections to retrieve current facts from corporate sources. He defined flows for querying Odoo, PostgreSQL and SQL datasets, CRM, accounting, sales, inventory, spreadsheets, and external data; combining financial and operational indicators; analysing variances and trends; and producing management explanations in natural language. The design includes access restrictions, validation, approval, auditability, and human responsibility for critical conclusions.

Reduces dependence on manual data gathering, shortens the path from a management question to an evidence-based explanation, improves consistency between operational and financial analysis, and supports repeatable reporting with appropriate governance.

Lead histories had to be reviewed individually to understand status, context, previous communication, and the appropriate next action. Inconsistent follow-up risked leaving viable opportunities inactive and made CRM housekeeping time-consuming.

Alexander designed an AI-assisted follow-up model with selection rules, structured fields, action logic, and technical execution through the Odoo API. The workflow covered historical-context extraction, lead classification, next-step determination, follow-up preparation, and task creation while retaining human control over customer-facing decisions.

Reduced repetitive CRM analysis, improved follow-up consistency, increased visibility into inactive opportunities, and made a large historical lead base more manageable without claiming outcomes not yet evidenced in conversion data.

Domain-specific work depended on fragmented tools, specialist knowledge, and repeated human analysis. Turning a sector problem into a digital product required simultaneous control of customer discovery, process design, product economics, technical architecture, and delivery.

Alexander led the initiatives as an entrepreneur and product owner, applying industry discovery, requirements analysis, product and unit-economics thinking, workflow design, architecture, prototyping, AI-assisted development, testing, and iteration. For the real-estate initiative, he designed an AI agent around property-selection work rather than a generic conversational assistant.

Shortened the path from domain problem to testable digital solution, made specialist workflows more explicit and repeatable, and created reusable product assets with the potential to scale beyond one-off consulting delivery. No unverified adoption or revenue outcome is implied.

Projects were managed through differing practices, roles, priorities, and reporting formats. Senior management lacked a common governance model for comparing initiatives, allocating resources, controlling risks, and connecting projects to organisational priorities.

Alexander created and developed Project Management Offices, designed corporate project-management methodologies, defined governance structures and roles, standardised planning and reporting, introduced portfolio prioritisation and project audit practices, and developed executive education programmes for project portfolio management.

Improved portfolio transparency and comparability, reduced dependence on inconsistent local practices, strengthened risk and resource oversight, and gave leadership a more structured basis for investment and prioritisation decisions.

The breadth of the portfolio and pace of delivery required clearer management responsibility and tighter coordination across product, commercial, operational, and financial functions. The company also had to remain prepared for M&A due diligence and international audit scrutiny.

As an operational and financial leader, Alexander formed a new management structure and connected operating decisions with financial oversight, product-portfolio management, international digital sales, SEO, and market demand. He participated in the M&A process and international audit from the COO/CFO side.

Improved organisational clarity and management control, supported repeatable delivery across a broad product portfolio, strengthened the connection between product operations and financial governance, and increased readiness for audit and corporate transactions. No unsupported valuation or financial uplift is asserted.

The sites depended on legacy WordPress infrastructure and accumulated content, media, redirects, and obsolete URLs. Migration risk included broken internal links, lost search visibility, missing assets, deployment errors, and difficult rollback.

Alexander personally managed content and media migration, URL inventories, redirect mapping, 301/404/410 analysis, internal-link validation, SEO preservation, staging and production deployment, backups, rollback planning, and post-release health checks. He built a Git-based deployment flow covering dependency installation, build, audit, synchronisation, and environment checks. For one site, a validated Astro build contained 203 pages and 15,305 internal links with zero broken internal links. He also implemented a server-side connection from website contact forms to Odoo CRM.

Reduced legacy infrastructure overhead, improved maintainability and deployment control, preserved content relationships during migration, lowered the risk of lost leads through broken forms or links, and created a cleaner technical platform for future content growth.

ERP work was inherently variable across industries, countries, business maturity levels, and implementation scopes. Sustainable delivery required a repeatable way to move from discovery and GAP-FIT analysis through implementation, integration, training, and ongoing support.

Alexander created a service model covering Odoo implementation, customisation, migration, hosting, integrations, BI, DWH/ETL, training, documentation, and support. He structured delivery around dedicated business analysis and L1/L2/L3 support, built and led developer and analyst capabilities, and standardised implementation offerings by module and complexity. The practice became an official Odoo Partner in Poland.

Improved predictability and accountability in ERP delivery, reduced knowledge loss between project stages, provided a scalable support structure, and made complex international implementations easier to govern over their full lifecycle.

Each additional entity and warehouse multiplied the number of stock movements, internal transactions, access rules, documents, and reconciliation points. Fragmented processes made it difficult to maintain one reliable view of inventory and group operations.

Alexander led the design and implementation of a multi-company, multi-warehouse Odoo architecture. He structured legal entities, warehouses, locations, product data, procurement and sales flows, intercompany rules, inventory movements, user roles, operational controls, reporting dimensions, data migration, testing, training, and production rollout. He aligned the configuration with the way the group actually purchased, moved, sold, and controlled goods rather than treating each warehouse as an isolated installation.

Turned organisational complexity into a controlled operating model, reduced the effort required to reconcile warehouses and entities, improved stock accountability, and created capacity for further expansion without rebuilding the information system for every new location.

Financial data originated in multiple legal entities and billing platforms. Budget control, liquidity management, management reporting, and group-level analysis depended on bringing different structures and transaction sources together. This increased manual consolidation effort and slowed management access to reliable information.

Alexander designed and implemented the group finance architecture: management charts and analytical dimensions, entity-level and consolidated reporting logic, budgeting, plan-versus-actual control, treasury and cash-flow processes, payment planning, billing-system integrations, data validation, and AI connections for controlled access to financial facts. He linked operational events with revenue, costs, receivables, payables, liquidity, and management reporting and established workflows for regular financial control.

Reduced dependence on spreadsheet-based consolidation, accelerated the preparation and interpretation of management information, improved liquidity and budget visibility, strengthened financial control across the group, and created a more audit-ready data foundation for executive decisions and growth.

Stock receipts, internal movements, issues, sales, purchasing documents, and financial records were not sufficiently connected to provide dependable operational and accounting visibility. Manual reconciliation increased the risk of discrepancies between physical inventory and financial data.

Alexander implemented the warehouse and financial management scope end to end. He structured products, units of measure, locations, receipts, deliveries, internal transfers, stock adjustments, procurement and sales documents, valuation logic, invoices, vendor bills, payments, reconciliation, permissions, reporting, data migration, testing, and employee workflows.

Improved inventory reliability, reduced manual reconciliation between warehouse and accounting records, strengthened responsibility for stock movements, shortened access to operational and financial information, and lowered the risk of losses caused by weak inventory control.

Marketplace orders, inventory held by the fulfillment provider, shipments, returns, product data, charges, and financial records existed in different systems. Staff had to monitor exceptions and reconcile Amazon, 3PL, ERP, and accounting data manually.

Alexander delivered the solution as a complete implementation. He designed Amazon order and product flows, integrated the ERP with the Mintsoft warehouse and fulfillment environment, configured inventory and fulfillment logic, mapped shipment and status exchanges, connected financial documents and reconciliation processes, implemented monitoring and exception handling, and added AI-assisted workflows for processing operational information and supporting user decisions. He managed requirements, architecture, implementation, testing, training, go-live, and support.

Reduced repetitive order and fulfillment administration, improved visibility of third-party stock and shipment status, lowered the risk of missed discrepancies, accelerated exception handling, and enabled marketplace growth without a matching increase in back-office workload.

Purchasing, incoming goods, landed costs, wholesale orders, online orders, retail transactions, stock, customer balances, and financial reporting crossed several operational channels. Separate records made product availability, margin, cash, and responsibility difficult to control consistently.

Alexander designed and delivered the complete ERP transformation. He connected supplier and procurement workflows, imports, receipts, landed costs, product and price management, B2B quotations and sales, e-commerce orders, POS transactions, warehouse operations, invoicing, payments, accounting, and reporting. The work included discovery, GAP-FIT analysis, process redesign, system configuration, integrations, master-data preparation, migration, testing, user roles, training, go-live, and post-launch support.

Eliminated major breaks between commercial channels and back-office execution, improved stock and margin visibility, reduced duplicate data entry, strengthened control over receivables and cash, and created an operating platform capable of supporting more products, customers, and channels.

Orders and operational data moved across several sales channels and a carrier network, while finance had to maintain correct invoices, payments, stock valuation, and statutory electronic-document flows. Manual transfer and reconciliation created delays and avoidable compliance risk.

Alexander implemented the project end to end: purchasing, product and supplier data, inventory, WooCommerce integration, Amazon and Allegro marketplace flows, InPost ShipX shipping processes, order and customer synchronization, fulfillment statuses, invoices, payments, accounting, Polish localisation, and KSeF readiness. He organised migration, exception scenarios, testing, user training, launch, and ongoing operational support.

Reduced channel-by-channel administration, accelerated order-to-shipment and order-to-accounting flows, improved stock and payment transparency, lowered the risk of inconsistent sales documents, and established a scalable and compliance-ready foundation for multichannel growth.

Direct-to-consumer orders, marketplace fulfillment models, warehouse stock, shipping execution, CRM activity, purchasing, and finance were distributed across specialised platforms. Differences between FBA, FBM, direct shipping, and ERP stock created significant reconciliation and exception-management complexity.

Alexander delivered the entire solution from discovery through production. He designed procurement and replenishment, warehouse accounting, product and SKU structures, Shopify integration, Amazon FBA and FBM processes, ShipStation shipping flows, Bitrix data exchange, customer and order synchronization, inventory updates, returns, accounting, payments, controls, reporting, training, and support. He defined ownership of data and exception rules so that operational teams could work across channels without losing traceability.

Reduced manual transfer between platforms, improved visibility across owned and marketplace-controlled inventory, accelerated fulfillment coordination, strengthened financial traceability, and enabled the business to operate multiple international sales and shipping models through a manageable back office.

The scale of the warehouse network and legal structure produced a large number of inventory, manufacturing, intercompany, purchasing, cash, and accounting events. Distributed teams needed common processes and skills; without them, group management depended on local practices, manual coordination, and delayed consolidation.

Alexander designed and led a large-scale multi-company implementation covering twenty warehouses, product and location architecture, procurement, replenishment, intercompany movements, manufacturing, bills of materials, production execution, stock control, sales, treasury, payment planning, accounting, group financial management, reporting, permissions, and a broad integration landscape. He translated local operating requirements into common group processes, supervised data and system readiness, and personally organised and delivered training for employees in Africa across executive, process, user, and technical levels.

Created group-wide operational visibility at a scale that would be impractical to control through spreadsheets, improved accountability for stock and cash, reduced dependence on local informal knowledge, strengthened financial governance, and established the process and training foundation required for sustained regional growth.

Goods and financial obligations moved between group entities as well as external suppliers and customers. Intercompany transactions, billing data, local accounting, balances, and group reporting had to remain aligned, creating repeated reconciliation and a high risk of inconsistent records.

Alexander designed and implemented the multi-company model for procurement, intercompany purchasing and selling, inventory movements, transfer pricing and document chains, billing-system integration, customer and supplier balances, group financial accounting, and local statutory accounting. He established data mappings, control points, roles, reporting logic, and exception handling and trained the African team to execute and maintain the complete process.

Reduced manual reconstruction of intercompany activity, improved the reliability of entity and group balances, accelerated financial reconciliation, strengthened local accounting control, and gave management a clearer view of how value and cash moved through the group.

Documents moved between employees and counterparties through separate files and communication channels. Editing, comments, approval status, revision history, and final versions were difficult to control consistently, while operational records lived in ERP.

Alexander designed a commercial document-management solution combining Odoo Documents with ONLYOFFICE. The architecture covered document upload, editing directly from ERP, collaborative work, comments, revision history, sequential approval, final approval, centralised storage, permissions, and links between documents and business records. He also evaluated the multi-client service architecture and commercial delivery model.

Reduced time spent locating and reconciling document versions, lowered the risk of acting on outdated or unapproved files, improved auditability, and created a repeatable document-control model for complex international trade operations.

Standard retail functionality did not by itself cover the country-specific fiscal workflow, device behaviour, document requirements, and operational exceptions required at the point of sale.

Alexander analysed the local requirements and designed the Odoo POS solution around KEP and SUNMI V2 PRO devices. He mapped the transaction flow from sale and payment through fiscal processing and accounting, defined hardware and integration behaviour, considered failure and retry scenarios, and prepared the system and user process for real retail operations.

Reduced dependence on disconnected fiscal actions, improved transaction traceability, simplified cashier operations, lowered operational compliance risk, and created a reusable architecture for controlled retail rollout.

Business analysts had to manually reconstruct requirements, decisions, contradictions, dependencies, and action items before they could prepare GAP-FIT conclusions, roadmaps, developer tasks, and test scenarios. Important context could be lost between discovery, presales, delivery, and support.

Alexander developed AI-assisted analysis workflows for processing transcripts and documents, extracting and grouping requirements by business process, identifying inconsistencies, separating business needs from proposed technical solutions, preparing preliminary scope, supporting GAP-FIT analysis, building implementation roadmaps, drafting developer tasks, and generating acceptance and test scenarios. He applied structured context, output schemas, validation rules, and human review so that AI accelerated analysis without replacing accountable solution decisions.

Shortened the transition from discovery to an actionable delivery plan, reduced repeated manual transcription and restructuring, improved continuity between commercial and technical teams, and lowered the risk that requirements or decisions would disappear during project handoffs.