The amount goes from the POS to the terminal, without being re-keyed. This is the connection that eliminates double entry.
Projexo Caisse
Making things that come from different systems work together.
Projexo connects your POS solution, your data and your equipment to avoid breaks and double entry.
What we doStudy, connect, migrate, check
With whomYour old system, your equipment, the publishers concerned
What you are left withA connected environment and migrated data
What connects
Around the POS, not everything has the same status
A desirable connection is not an existing connection: each one here carries its real status.
At the centreYour POS solutionEverything that follows connects to it, or does not connect to it yet.
Each line goes to the station that prepares it: the destination is set during configuration.
Opened by the POS at the time of payment, or by the printer depending on the software.
The barcode or the weight goes straight into the sales line.
Managed by the POS software itself. What is available depends on the plan subscribed.
Announced by the three publishers, at different plan levels.
At the heart of the beauty solution; to be studied elsewhere.
No connector is announced on this site until it has been verified for your platform.
Most often by end-of-period export, taken into your accounting tool.
Provided by the software. Export to a spreadsheet remains the most common route.
Direct connectionThe hardware plugs into the terminal and we check it on site.
Announced by the publisherPublished on the software's official pages. Remains to be verified for your configuration.
By import or exportNo automatic link: a file passes from one system to the other.
To be studied at the auditNothing is promised until feasibility has been verified on your premises.
Why we do not publish a compatibility list
A compatibility announced without having been tested on a real installation is a promise someone will have to keep on switchover day. Until we have connected a tool at a client's, it remains "to be studied" — and the study is part of the audit.
Data migration
From one system to the other, in seven stages
Migration is not improvised on switchover day: it is prepared and tested beforehand.
Old system
We look at what it contains and, above all, what it agrees to export. That limit decides everything else.
What comes outAn inventory of what can be recovered
Export
The file comes out in the format the old tool offers — rarely the one we would have chosen.
What comes outA dated source file
Clean-up
Duplicates, inconsistent labels, obsolete prices, dead items. What is no longer used is not migrated.
What comes outA clean data set
Field mapping
Every column in the old system finds its place in the new one, or does not — and that is stated.
What comes outA mapping table
Test import
On a test environment, never directly in production.
What comes outA verifiable import
Checking
We count, we compare, we open records at random. Discrepancies are corrected before, not after.
What comes outA discrepancy report
Go-live
The switchover, on a date chosen with you, once checking has passed.
What comes outThe new system in service
What migration depends on
What the old system agrees to export, the quality of what it contains, the formats available and the new publisher's rules. These four points are verified at the feasibility study, and whatever cannot be migrated is announced before the switchover, never after.
Before / after
What a completed integration changes
The same hardware, the same software: what changes is what flows between them.
On arrival
- The amount is re-keyed on the payment terminal
- Items exist in two versions, in two tools
- The accounting export is redone by hand every month
- Every peripheral was plugged in by someone else
- When a link breaks, nobody knows who to call
On leaving
- The terminal receives the amount from the POS
- A single reference catalogue, migrated and checked
- An export in the format your accountant expects
- Every link tested on the real terminal before going into service
- A point of contact who connected the whole thing and knows it
These states describe a delivered installation, not a measured gain: we publish no percentage of time saved until it has been recorded at a client's and authorised by them.
Who does what
An integration brings several parties round the table
We coordinate: that does not mean we decide in their place.
You
What you provide or approve
- Access to the old system and to the tools being kept
- Current contracts: licences, payment, operator
- Approval of the field mapping table
- The choice of switchover date
- Checking the data once migrated
Projexo
What we carry out
- The feasibility study for each link
- The inventory of connections required
- Data preparation and clean-up
- Testing before the switchover and checking afterwards
- Coordination of those involved
Publisher or third party
What does not depend on us
- The export formats of your old system
- The new publisher's import rules
- Whether or not a connector to a third-party tool exists
- The payment provider's terms
When a link does not exist, no integrator can create it: we say so at the study stage, and we then propose going through import or export if that is possible.
What you are left with
What is written down and handed over
An integration is documented: otherwise nobody can take it over.
What is connected, what goes through a file, what remains to be studied.
Link by link, what is possible and on what terms.
How each field in the old system ends up in the new one.
The cleaned data set, as it was loaded.
What was checked before the switchover, and the discrepancies corrected.
These documents are produced for the integrations we carry out. Their exact form depends on the scope: it is set in the quote.
Our expertise
Five trades that follow one another
Each one prepares the next: that is what makes the difference between an integrator and a reseller.
Consulting and workflow auditUnderstanding how you operate before recommending anything at all.Integration and migrationMaking the software, data, hardware and your tools hold together.Installation and configurationHardware prepared, connected and tested before the first customer.Team trainingThe team at ease on your configuration, not on a demo.Support and maintenanceA point of contact who knows your installation when something gets stuck.
Let's identify what needs to be connected, migrated or simplified.
We look at your current environment, we check link by link what is possible, and we write down what is not. Before starting, not after.
Your quote, itemised line by line.
An audit of your workflows, then a quote detailing every item and a rollout schedule set with you.