smart skladište. AI automatizacije · postojeći sustavi
EN / HR Book a call →
EN / HR Book a call →
// METHODOLOGY

We don't start at the screen. We start at the shelf, the goods, the waybill, the scanner, the people.

Practical AI automation starts with one question: what's actually working today, and where are people manually patching the system? Only after that do we define what to connect, automate or build — document flow, email, orders, eInvoice, ERP integrations, reporting or a physical process in the warehouse. One workflow, built around your actual operations.

Three phases of our approach

Process mapping (real work)

We map how the work actually moves through your company.

We trace the workflow from the first trigger to the final report, document or dispatch. We identify manual entries, duplicated work and the points where systems stop talking.

  • ERP, Excel and email — where the first manual entry happens
  • Document & order flow — where the same data gets retyped across systems
  • Warehouse steps — where scans or checks can remove retyping
  • Documents — receiving notes, waybills, returns, contracts
  • ERP / Excel overlap and the eInvoice flow
Duration 1–2 wk

Pilot on one flow

We test without stopping operations. The pilot can be one goods flow, one document flow, one report, one email flow or one integration — whatever has a clear output.

We pick one flow and run the integration in parallel with the existing work. Operations keeps moving; we measure where the pilot actually changes things.

  • Definition of "success" before we start
  • Parallel work — old and new flow side by side
  • Measurement: errors, time, manual entries
  • Go / no-go decision before scaling
Duration 2–4 wk
pilot · p. 4
Parallel run
EXISTING FLOW PILOT FLOW in parallel

We measure errors · time · manual entries.

Phased implementation

We scale where it makes sense. We leave alone what works.

ERP, Excel, email, documents, orders, scanners and reports get wired into one flow. Automation enters where it cuts manual work. Teams train during the parallel run — no "big go-live day."

  • Existing ERP kept and integrated
  • Excel and email connected where they still support the work
  • Scanners / RF terminals where they cut manual entry
  • Documents (eInvoice, waybills) automated
  • Rollback plan + post-go-live support
Duration 6–16 wk

What we don't do.

The difference between practical embedded automation and a classic software project.

  • We don't force an ERP shutdown.

    If your ERP handles accounting well, we don't touch it. We wire the workflow into it.

  • We don't sell SaaS subscriptions.

    Project investment with defined scope. Optional support, not a mandatory monthly license forever.

  • We don't implement without understanding the workflow.

    No process mapping, no proposal. If the problem doesn't justify a project — we'll tell you.

  • No "big bang" go-live.

    No single date by which everything has to work. Phased, parallel, tested before cutover.

What we automate.

Warehouse flow is our deepest specialty. But the method — mapping, pilot, phased implementation — works for any process where people manually bridge systems.

  • Warehouse flow

    Picking, packing, dispatch, stock counts, RF terminals. Our deepest specialty, connected to ERP, documents, orders and reporting instead of living in isolation.

  • Documents

    Receiving notes, waybills, returns, contracts. Automatic classification and approval flows without retyping into Excel.

  • Orders & sales

    Webshop sync, B2B orders, dispatch-to-stock matching, e-mail automation. One source of truth on an order from web to dispatch.

  • eInvoice & finance

    eInvoice flow, control processing, payment matching, reports. Compliance as a natural part of the flow, not a separate package.

  • Integrations

    ERP connectors, courier APIs, BI dashboards, custom workflows and internal tools. We wire together systems that weren't talking to each other.

The biggest ROI comes when more than one flow runs through the same workflow.

What we connect to.

We don't force replacement. We wire existing systems together.

  • ERP
    • SAP
    • Microsoft Dynamics
    • Odoo
    • Pantheon
    • Synesis
    • custom / in-house
  • Warehouse hardware
    • Zebra
    • Honeywell
    • Datalogic
    • RF terminals
    • Wi-Fi scanners
  • Documents
    • eInvoice (Fina, Moj-eRačun)
    • receiving notes, waybills
    • returns
    • DPS / reports
  • Logistics
    • DPD · GLS · DHL · Overseas
    • own fleet
    • Shopify
    • WooCommerce
    • Magento

The biggest fears before a project.

Questions we hear every week — and how we handle them.

  1. "What if it doesn't connect to our ERP?"

    First we run a technical integration review — what the ERP exposes (API, databases, exports), where we can hook in and where we can't. The pilot runs on a limited scope; only after validation do we scale.

  2. "What if operations go down?"

    Phased implementation with parallel work. Every phase has a rollback plan. No "big bang" go-live — test scenarios are run before cutover.

  3. "Our workers won't use it."

    The system is built around how people actually work — not an ideal flow from a slide deck. Training happens during the parallel run, so workers digest the new flow before cutover.

  4. "I don't want another monthly license forever."

    Project investment with scope. Optional support after go-live. You own the system — no dependency on a vendor for every small change. The workflow stays yours — the code is documented, ownership is yours, you don't depend on us for every change.

  5. "We already tried software and it didn't stick."

    Likely because it started from the screen, not the process. Our approach reverses that — workflow first, proposal second. If the mapping shows the issue isn't software, we'll tell you.

Not sure where it's breaking? Book a practical call.

30 minutes of practical conversation. No sales pressure. If automation would not help, we'll say that. Your existing systems, your process, a phased way forward.

Book a call