Data Management

CSV exports

These are the CSV endpoints you'll find linked from various admin pages. All require an authenticated session with the right role for the data you're fetching.

• Products — /products.csv. Your market's product catalog.
• Orders — /orders/export.csv. Orders in a date range.
• Order items — /orders/export-items.csv. Line-item-level detail across orders in a date range.
• Users — /users/export.csv. Shopper, grower, and staff accounts for your market.
• Order items by order — /order_items/export.csv. Scoped line items for reconciliation.
• Grower checks — /orders/checks.csv. What each grower is owed for a given period, including commission math.
• Harvest history (per grower) — /orders/harvest_history/{growerId}/csv. A grower's sales history.
• Impersonation audit — /admin/impersonation-audit/export.csv. The admin impersonation audit log; superuser-only.

Exports stream as-you-request; there is no background-processing queue, no email-when-ready flow, and no stored export history.

PDF reports

PDF output exists for a specific set of operational reports, generated live from the orders area:

• Per-order invoice
• Packing report
• Sales report
• Sales by pickup location
• Orders by pickup location
• Open invoices
• Harvest labels

These are linked from the admin orders and reports pages. See the Reports guide for context on when to use each.

Bulk import

LocallyGrown does not currently offer a bulk-import UI. Products, customers, categories, and pickup locations are entered through the admin UI. If you're migrating from a spreadsheet or another platform, plan on either manual entry, or getting in touch so we can talk about a one-off data load.

Backups

Platform database backups are a LocallyGrown operational responsibility, not a market-admin feature. There is no "Create Manual Backup" button, no downloadable backup file, and no self-serve restore. If you're worried about a specific destructive change, the right move is to export the affected data as CSV before you make it.

If you suspect data loss, contact support as soon as possible — recovery options depend on how recent the change is.

Privacy-related requests

LocallyGrown does not maintain a formal GDPR / CCPA compliance program. For the user-visible tools that exist today:

• Shoppers can update their own profile, change their password, and deactivate their account from their account page.
• Admins can export user records for a market as CSV (see above) and edit or deactivate accounts from the admin UI.
• Order history is preserved after account deactivation for market recordkeeping (see the Shopper Accounts guide).

If your market operates under a regulatory regime that requires more than this — data portability in a specific format, a formal "right to erasure" workflow, a signed DPA — reach out via support before rolling out.

Practical tips

• Date-range your exports. The order CSVs accept a date range; keep it narrow unless you actually need the full history, especially on large markets.
• Keep your own copies. Archive important exports (year-end sales, 1099-eligible grower totals) somewhere you control rather than relying on being able to regenerate them later.
• Test destructive changes in small batches. There is no undo for things like category deletion or bulk product deactivation — the safest workflow is a CSV export first, then the change.