Import Center & API/ERP Bridge: Bring Data In Without Bringing Chaos
How CSV, API push, import jobs and ERP setup fit together for teams that already have systems.
Integrations usually start with a practical problem: data exists somewhere else. Sometimes that means a one-time CSV. Sometimes it means an ERP pushing assets every day. ReVend OS supports both patterns, with different expectations.
Manual imports
General imports and module-specific import screens handle files such as companies, contacts, inbound manifests, sellable inventory and audit-tool outputs. They should validate rows, show skipped or failed records, and keep source context visible. A file import is not a trust fall.
API push
Non-Core tenants can push sellable assets through the API, group them into lots, and publish to Market or Auction. Core records can also be created and transitioned through guarded API endpoints where the integration owns part of the lifecycle.
Import jobs
The import-job API currently registers requests without processing or validating their files. Dry runs and validation-only requests also remain registrations; an empty error list does not confirm a valid file. The monitor excludes these previews from actual imported records and completed imports. Cancelling a registration preserves any recorded partial results. Use the supported immediate bulk endpoints when data needs to be processed.
ERP setup
/general/imports/api-erp and /settings/integrations provide the setup context for ERP-style work. The rule is simple: decide which system owns which fields before syncing. Otherwise two systems can spend the afternoon politely overwriting each other.