Bulk import and export -- getting products, orders, or customers in and out as CSV or Excel rather than one at a time -- is routine, unglamorous work. It's also exactly the kind of feature where a small oversight (a missing tenant filter, a query that trusts a file's contents blindly) turns into someone seeing or overwriting data that isn't theirs.
What real bulk import/export needs, beyond "it works"
Genuine validation on the way in -- checking required columns and values are actually present and sane before committing anything, not discovering a malformed row only after it's already corrupted a record. Resilience per row, so one bad line in a 2,000-row file doesn't abort the entire batch or, worse, leave it half-applied. And on a multi-tenant platform specifically: every query and insert explicitly scoped to the current tenant, not relying on a single layer of protection to catch everything.
How Vedron handles this
Vedron's import/export supports products, orders, and customers, exporting to CSV or JSON with column selection and company/date filtering, including a streaming path for larger datasets rather than choking on volume. Imports accept CSV and Excel, validate required columns and values before committing, and process rows independently -- a bad row is reported (capped at a readable error list, not a wall of noise) rather than silently failing the whole import or partially applying it.
Every query and insert in both the import and export paths is explicitly scoped to the current tenant in the code itself, not left to a single mechanism to enforce -- deliberate defense in depth, so a failure in one layer doesn't expose or corrupt another tenant's data. On a shared multi-tenant platform, that's not a nice-to-have; it's the difference between a bulk operation being routine and being a real risk.
Frequently asked questions
What happens if my import file has a few bad rows mixed in with good ones?
Good rows are processed; bad ones are reported with enough detail to fix and re-import, rather than the whole batch failing because of a handful of problem rows.
Can I export just a date range or a specific set of columns?
Yes -- exports support column selection and date/company filtering, so you're not stuck exporting everything every time.
Does this work for very large catalogs or order histories?
Larger datasets use a streaming export path specifically so volume doesn't become a practical blocker.
Have a question specific to your setup?
Every seller's marketplace mix and stock setup is a little different -- if you're weighing this against your own, book a short call and we'll walk through it with you directly rather than leaving you to figure it out from a blog post alone.
Beta offer: if you join as a beta client, custom integration setup -- configured for your actual marketplace and inventory mix -- is free for your first 2 months.
Still evaluating and need more time than the standard trial window? Just ask us for an extension -- we're happy to give you the room to actually test it properly before deciding.