Integrations
Keep the system your pharmacy already uses.
RowBotic adds a physical intelligence layer on top of your existing pharmacy software — it does not ask you to replace it.
Integrations
It sits alongside what you already run.
Adapter architecture
PLEX-first, canonical-events everywhere else.
Adapter architecture — PLEX (first integration target)
- PLEX
- PLEX adapter
- Canonical RowBotic events
- Core platform
Planned adapters (not yet live)
Domain logic is never coupled to a vendor's tables. RowBotic never writes to production ERP tables outside documented, vendor-supported mechanisms.
Rollout
Integration depth grows with trust.
- 1
CSV / report import
For prototyping and early pilots.
- 2
Authorized read synchronization
Documented, permissioned read access.
- 3
Near-real-time adapter
Event-driven sync as the integration matures.
- 4
Vendor-supported deep integration
Full integration once supported by the vendor.
FAQ
Common questions
- Does RowBotic replace my pharmacy system?
- No. RowBotic is designed to integrate with your existing pharmacy management software — sales, billing and health-plan validation stay in your current system.
- Which system is the source of truth for what?
- Sales, billing and health-plan validation remain in your existing POS/ERP. Physical locations, pick tasks, device state and the shelf map are owned by RowBotic.
- Will RowBotic write directly to my ERP's database?
- No. RowBotic never writes to production ERP tables outside documented, vendor-supported mechanisms — integration always goes through an adapter.
Pilot program
Run a measured pilot in your pharmacy.
We instrument the pilot from day one — baseline search times, pick times and location accuracy — so results are measured, not assumed. No ERP replacement, no structural installation required.