Data Export v2 Architecture

How subscription exports work in CoEditor—flow, what you configure, and what you receive in the CSV.

Names and scope

In the CRM this area is Data Export with the subtitle “subscription data exports”. Data Exports v2 (beta) in the publication sidebar focuses on subscription CSV generation with filtering, labels, templates, and scheduling.

It complements legacy Data Exports (issue-scoped v1 under /publications/{id}/data-exports). Most operational workflows use v2.

Open the dashboard: /publications/{publicationId}/data-exports-v2

How an export runs

sequenceDiagram
  participant User as CRM user
  participant CRM as CoEditor CRM
  participant Job as Background export job
  participant Store as File storage

  User->>CRM: Submit Create subscription export
  CRM->>CRM: Save snapshot (pending)
  CRM->>Job: Start generation (async)
  Job->>Job: Build rows from Stripe + CRM
  Job->>Store: Upload CSV
  Job->>CRM: Mark snapshot success or failed
  User->>CRM: Download CSV when ready

You submit the Create subscription export form in the CRM.
CoEditor creates an export snapshot on the dashboard (status pending).
Generation runs in the background—the CRM does not block until the file is ready.
When complete, status becomes success and Download is available, or failed with a status message on the row.
Optional labels, templates, and scheduled runs reuse the same configuration shape.

What you provide

Path: /publications/{publicationId}/data-exports-v2/create

Input	What to provide	Notes
Export name	Short label for this job	Shown on the dashboard
Stripe account	Connected account to query	Default = publication primary
Products	Stripe products or all on the account	Defines which subscriptions are in scope
Subscription dates	Optional start and end	Limits the subscription window
Column scope	All or Custom	See What you receive
For fulfilment	Checkbox	On for print/mail/warehouse; off for reporting-only
Label	Optional	Organises exports on the dashboard

Fulfilment / print issue fields

When For fulfilment is enabled:

Field	Format	Purpose
Issue name	Text	Print issue or fulfilment batch
Cover date	`YYYY-MM-DD`	Cover date
Release date	`YYYY-MM-DD`	Release date
Print date	`YYYY-MM-DD`	Print or mail date

Use YYYY-MM-DD for these dates so the stored issue date does not shift by timezone.

Templates and scheduling

Templates — save form settings (except export name) for reuse via Manage templates.
Scheduled exports — second dashboard tab; completed runs link to a result snapshot.
Edit pending schedules: ?editScheduled={id} on the create URL. Edit templates: ?editTemplate={id}.

What you receive

Snapshot on the dashboard

Each run appears as a row with name, status (pending | success | failed), progress, optional label, and manual vs scheduled source.

Detail view: /publications/{publicationId}/data-exports-v2/{exportId}

CSV file

One row per matching subscription. Headers match the fields selected on the form.

Column scope	Contents
All	Full customer and subscription field set (identity, contact, shipping, billing, lifecycle, coupons, publication/issue metadata, etc.)
Custom	Only fields ticked under Customer information

Representative columns include name, email, phone, customer and subscription ids, product and price ids, shipping address, amounts, interval, and issue name. The create form column preview is the authoritative list for your publication.

Scheduling and templates

Scheduled exports store the same parameters as a manual run. When a schedule fires, CoEditor creates a new snapshot and processes it the same way.

Templates store a fingerprint of product selection, dates, column scope, fulfilment flag, and print issue fields so teams can rerun consistent exports without reconfiguring the form.

Date handling

Cover, release, and print dates should be sent as calendar dates (YYYY-MM-DD) from the CRM form. Full timestamps can shift the stored day for users in some timezones.

Data exports overview
Integrations
App API Routes — cancellation APIs (separate from CSV exports)

Data Export v2 Architecture

On this page