Integrations

    How data gets into buffers.ai

    buffers.ai connects to SAP, Oracle, IBM AS400, Priority, Microsoft Dynamics, and many custom-built ERPs. Here's what's supported, what data is required, and how a rollout gets scoped.

    See how it works
    Supported ERPs

    Connects to the ERP you already run

    Connectors for the major ERP platforms, plus many custom-built, in-house systems.

    SAP

    SAP ERP systems

    Oracle

    Oracle ERP systems

    IBM AS400

    IBM i (AS/400) based ERPs

    Priority

    Priority ERP

    Microsoft Dynamics

    Dynamics 365 and earlier Dynamics ERPs

    Custom-built ERPs

    Many in-house and heavily customized systems connected

    Two Paths In

    Evaluate with a file. Go live with a feed.

    To evaluate: share a sample file

    Share a CSV or XLSX export of your own sales history with our team and it runs through the same five-algorithm backtest used in production — no ERP work required to see how it performs on your catalog.

    To go live: connect your ERP

    Production rollouts run on a recurring feed from your existing system — through a connector for SAP, Oracle, IBM AS400, Priority, or Microsoft Dynamics, a custom integration with an in-house ERP, or batch/FTP exchange (as in the RAI case study).

    buffers.ai connects to SAP, Oracle, IBM AS400, Priority, and Microsoft Dynamics, and to many custom-built ERPs. Whatever the source system, the team handles catalog-specific details like fractional units, weight-based products, and vendor-specific naming. Running something not listed here? Ask directly — custom ERPs are a routine part of rollouts.

    Minimum Viable Data

    Three columns are required

    One row per SKU per day. Everything beyond the three required columns is optional and depends on your catalog.

    Required

    date
    Calendar day, YYYY-MM-DD
    sku
    Product / SKU identifier
    sale
    Units sold that day (0 on no-sale days)

    Optional, if you have it

    SeasonColorSizeMaterialPriceCategoryStore / locationChannel

    Never required, but the more consistently they're filled in, the more the forecasting models can learn from them.

    Existing Systems

    Working with your existing stack

    On RAI's rollout — a grocery retailer managing 6,000–7,000 SKUs — buffers.ai's team worked directly with RAI's internal developers to configure FTP-based data exchange with their existing ERP, handle fractional and weight-based units, localize product naming for vendor communication, and resolve unit inconsistencies across suppliers, with ongoing technical support as the integration matured. That's the model for custom and in-house systems: configuration around your system, not a requirement to adopt a new one.

    Full write-up: How RAI saved 3 hours per day per store manager.

    FAQ

    Frequently Asked Questions

    Tell us your stack, we'll scope the integration

    SAP, Oracle, IBM AS400, Priority, Microsoft Dynamics, or a custom-built ERP — tell us what you run, plus your POS or WMS, and we'll scope the rollout.

    Back to buffers.ai