DOT's retail ecosystem: what it includes and how you assemble it
Eight pieces sharing the same stock, the same pricing and the same customer. Take them all, or start with one and add later.

An ecosystem is not a discounted bundle of products. It's a set of pieces that already talk to each other: they share one data core, so stock, pricing and the customer are the same in the store, in e-commerce and in mobile selling.
That's the difference: nothing to integrate, and nobody to chase when the problem sits between two systems.
The eight pieces
Each line is a native integration: data flows on its own between the pieces, no retyping.
How you assemble it
You can take the full ecosystem or start with one piece. Neither is more correct: it depends on where you are today.
All at once makes sense when opening a new operation or replacing a system that's run out of road: everything arrives pre-integrated, with one party accountable.
Piece by piece is the common path. Start where it hurts most today; each piece runs on its own, and the next one arrives already connected, with no integration project in between.
- If the pain is the queue at peak hours →
Mobile One. - If stock doesn't match across channels →
Retail Pro Prism. - If you can't tell which store made margin →
BiPyxis. - If you need to meet SII rules → DTE.Electronic invoicing.
Already running an ERP? The ecosystem is built on SAP Business One, but it also integrates with whatever ERP your company already uses.
In short
- Eight pieces on one data core, with
SAP Business One at the center. - Take them all, or start with one.
- Each runs on its own; adding the next is not an integration project.
DOT Solutions has been implementing this ecosystem for over 16 years, with more than 300 clients across 8 Latin American countries.

