Implementation
Your first operation live in 90 days.
Without replacing your ERP and without a year-long project. We start with the process that hurts most, measure it against criteria you sign up front, and add modules in phases.
00Before the contract
Prove it first, sign after.
Before the implementation contract we run a focused pilot in your warehouse, with real 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
BeforeRemote
Document formats, location map, users and devices ready before day 1.
Days 1 and 2On site
Kickoff visit: installation, training and the first operations run side by side.
Days 3 to 5Remote
Your people run the operation. We follow up remotely.
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, not at the end of the project.
Week
- 01Site survey and functional design
- 02Entry module in production
- 03Outbound, transport and integration
- 04End-to-end test and go-live
- 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.
- 02
Weeks 4 to 7
Entry module 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 Etiqueta Zero.
Deliverable
Locatable inventory: every pallet in a scan-confirmed position.
- 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.
- 04
Weeks 11 to 13
End-to-end test and go-live
What happens
An end-to-end run on the real operation, training for users and supervisors, and a gradual release. Adjustments follow what the operation shows, not assumptions.
Deliverable
Signed go-live report and a stabilized operation.
How long it really takes
- Basic routing
- 4 to 6 weeks
- WMS and routing
- 2 to 3 months
- Full platform
- 3 to 4 months, in phases
Traditional ERP suites usually take 6 to 12 months for equivalent modules. 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.
A project this size is won or lost on scope decisions. That is why the rules are set 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: signature, operation in production, integration and testing, accepted go-live.
- Measure before promising
- We do not promise percentages before 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 at least 20 real receipts:
- C1
The document arrives before the truck
Waybill, delivery note or bill of lading loaded and linked to customer and reference before arrival.
- 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 on the spot, not at close.
- C3
Every package with its owner
No package is linked to a customer or reference other than the one on its document.
- 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.
- 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 real 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 pays off on its own.
Let's design your first 90 days.
In a demo we review your operation, the entry process and what is worth measuring in the pilot.