ERP, WMS & Integrations
ERP brings your key business data together in one place. WMS runs the warehouse — receiving, inventory, picking, and shipping orders.
What the ready core covers
Manage
ERP and WMS core, inventory, reports, roles, permissions, and administration.
Connect systems
Ready-made integrations and custom links. The public API, automatic system-to-system notifications, and the universal connector engine are being finished.
Inventory, ERP, and WMS
ERP brings your key business data together in one place. WMS runs the warehouse — receiving, inventory, picking, and shipping orders.
- Available nowA ready ERP and WMS core for products, SKUs, inventory, orders, payments, shipping, returns, and reports.
- Available nowInventory tracking and alerts for low or out-of-stock items.
- Available nowSynchronization between the store, orders, carriers, and warehouse operations.
- Available nowEach tenant — a separate customer profile on the platform — uses its own isolated configuration and its own data.
- Available nowConnecting external ERP systems via API, file exchange, or a dedicated connector, when the external system provides suitable technical access.
- Beta / partialA standard external-ERP integration can be delivered within 30 calendar days after written approval of the scope and after receiving full technical documentation, valid APIs or file formats, the required access, a test environment, and quality test data. The timeline also depends on the external ERP vendor’s cooperation; non-standard integrations are planned separately.
- In developmentFull multi-warehouse and multi-location management, stock transfers between them, purchase orders to suppliers, and automatic replenishment requests.
- In developmentAdvanced barcode and scanning processes for receiving, picking, and warehouse control.
API, integrations, and developer platform
An API is a standard way for external systems to exchange data with NEXT BASKET AI. Through it, the platform can connect to ERP, CRM, accounting, warehouse, and other applications.
- Available nowReady-made direct integrations with payment systems, carriers, marketing channels, and product feeds.
- Available nowImport and export via CSV and XML.
- Available nowCustom integrations built to spec for a specific tenant (a separate customer profile).
- Beta / partialArchitectural groundwork for a public API and separate integration services.
- In developmentA public admin API and a Storefront API for external storefronts.
- In developmentInbound and outbound webhooks, an event bus, duplicate protection, automatic retries, delivery logs, and replays.
- In developmentA universal connector engine and ready-made links to Zapier, Make, n8n, and Pipedream.
- In developmentA connector development kit (SDK), an app catalog, and tools for external developers.
External ERP integration timeline
The 30-calendar-day timeline is not an unconditional guarantee. It applies to a standard integration with a pre-approved scope and starts after we receive full technical documentation, valid interfaces or file formats, the required access, a test environment, and quality test data. The timeline also depends on the external ERP vendor’s cooperation. Non-standard integrations are assessed and planned separately.
The technical foundation
One cluster serves many stores — with each store’s data logically isolated.
NEXT BASKET is multi-tenant: a single platform hosts hundreds of separate stores. Each tenant has its own configuration and logically isolated data, and our regular restore verification covers every tenant. The platform runs on managed data stores, so backups, replication, and upgrades are handled by specialized providers.
We list a feature as available only when it’s ready for real-world use on the applicable plan, country, and contract. Modules that work but are limited are marked Beta. Roadmap features are never presented as finished. Availability may depend on the plan, country, contract, and the specific integration.