Skip to content
Geodot

Implementation

Your first operation live in about 90 days.

Without replacing your ERP and without a year-long project. We start with the process with the greatest impact, measure it against criteria you sign up front, and add modules in phases.

Request a demoHow we handle your data

00Before the contract

Prove it first, sign after.

Before the implementation contract we run a focused pilot in your warehouse, with your own goods and your own people.

Success criteria come out of the site survey, are signed when the pilot starts and are measured on that week's operation. Once the results report is approved, the implementation is signed, and what you paid for the pilot can be credited toward it as agreed in the proposal.

One week of operation

  1. BeforeRemote

    Document formats, location map, users and devices ready before day 1.

  2. Days 1 and 2On site

    Kickoff visit: installation, training and the first operations run side by side.

  3. Days 3 to 5Remote

    Your people run the operation. We follow up remotely.

  4. CloseRemote

    Criteria measured and results report signed over a video call.

Thirteen weeks, four phases.

Every phase ends in a deliverable that is reviewed and approved. Your operation runs under digital control from the first week of each phase.

  1. 0

    Week 0

    One week of operation

    1. BeforeRemote
    2. Days 1 and 2On site
    3. Days 3 to 5Remote
    4. CloseRemote

    Pilot report with the signed criteria

  2. Contract signature

    Payment tied to the milestone
  3. 1

    01Weeks 1 to 3

    Site survey and functional design

    Digital control from week 1

    Deliverable

    Validated functional map and signed go-live criteria.

    Sign-off · week 3

  4. 2

    02Weeks 4 to 7

    First process in production

    Digital control from week 4

    Deliverable

    Locatable inventory: every pallet in a scan-confirmed position.

    Sign-off · week 7

    First process live
  5. 3

    03Weeks 8 to 10

    Outbound, transport and integration

    Digital control from week 8

    Deliverable

    Validated outbound and ERP exchange working.

    Sign-off · week 10

    Integration and testing
  6. 4

    04Weeks 11 to 13

    End-to-end test and go-live

    Digital control from week 11

    Deliverable

    Signed go-live report and a stabilized operation.

    Sign-off · week 13

    Accepted go-live
  • Milestone with sign-off
  • Payment tied to the milestone
  • Operation under digital control from the first week of each phase
  1. 01

    Weeks 1 to 3

    Site survey and functional design

    What happens

    We walk the operation with you: documents, docks, locations, roles and customer rules. Together with your IT team we define how we connect to the ERP.

    Deliverable

    Validated functional map and signed go-live criteria.

  2. 02

    Weeks 4 to 7

    First process in production

    What happens

    We configure the warehouse, load the active catalog and conversion factors, and start the highest-impact process. Usually: receiving, inventory and labeling with iWMS and Zero Label.

    Deliverable

    Locatable inventory: every pallet in a scan-confirmed position.

  3. 03

    Weeks 8 to 10

    Outbound, transport and integration

    What happens

    Dispatch with scan validation, customer rules and exception control. Transport and Control Tower join if they are in scope, and the ERP receives the status of every operation back.

    Deliverable

    Validated outbound and ERP exchange working.

  4. 04

    Weeks 11 to 13

    End-to-end test and go-live

    What happens

    An integrated test on the live operation, training for users and supervisors, and a gradual release. Adjustments follow what the operation shows.

    Deliverable

    Signed go-live report and a stabilized operation.

Timelines by scope

Basic routing
4 to 6 weeks
WMS and routing
2 to 3 months
Full platform
3 to 4 months, in phases

The final schedule depends on scope and on what your ERP exposes.

What your team brings and what we bring.

Your team

  • A project owner with decision authority who sits on the steering committee.
  • One operations person assigned during the pilot and the rollout.
  • Key warehouse, transport and supervisor users for training.
  • Sample documents, product catalog and the warehouse's physical map before preparation.
  • Technical access to the ERP or its exports, coordinated with your IT team or vendor.
  • Hardware on site before day 1: scanners, label printers and Wi-Fi.

Geodot

  • Site survey, functional design and platform configuration.
  • ERP connection through whatever path it allows: API, files or connector.
  • On-site kickoff visit and remote follow-up.
  • Training for users and supervisors, and hands-on support at rollout.
  • Operational reports: receipts, discrepancies, stock, tasks and incidents.
  • Support in Spanish, with teams in Mexico and Argentina.

Hardware (scanners, printers and network) is not part of the implementation.

Project governance.

Scope, deliverable and payment rules are written down before we start.

Steering committee
Your project owner and Geodot's review progress, risks and decisions. Anything that changes scope is decided there, in writing.
Written scope
What the scope annex lists is what gets delivered. What it does not list is quoted separately, before the work is done.
Milestones with sign-off
Every phase closes with an approved deliverable, and implementation payments are tied to those milestones: contract signature, first process live, integration and testing, and accepted go-live.
Measure before promising
Percentages are defined after the pilot. Times, discrepancies, productivity and incidents are visible in reports from day one.

What working means.

Go-live criteria come out of the survey of your operation and are signed up front. This is how they look in a warehouse receiving pilot, measured over a minimum of 20 receipts:

  1. C1

    The document arrives before the truck

    Waybill, delivery note or bill of lading loaded and linked to customer and reference before arrival.

  2. C2

    What was received matches what was expected

    100% of the packages in each receipt are reconciled against the document. Shortages and overages are reported at the time of receiving.

  3. C3

    Every package with its owner

    No package is linked to a customer or reference other than the one on its document.

  4. C4

    No manual relabeling

    Origin barcodes are read when their structure allows it. If not, the system prints the pallet label when the pallet is built.

  5. C5

    Location confirmed by scan

    Every pallet sits in a scanned position, and a lookup by customer or reference returns where it is.

After go-live.

Stabilization

Final adjustments on the operation, advanced team training and intensive support in the weeks after rollout.

Support and maintenance

An annual contract from the start of production: incident handling, operational questions and functional guidance for admin users.

Next phases

Once the core operation is stable, we evaluate the next module with you: routing and palletizing, transport, cold chain or document management. Each module can run on its own.

Your first 90 days, in writing.

In the demo we review your operation, the first process and the criteria worth measuring in the pilot.

Request a demo