Onboarding Import: Editions

From PubGizmo Help
Revision as of 19:24, 4 June 2026 by PubGizmoSysop (talk | contribs) (Claude conversion from PG site)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Part of the Onboarding Import series.

The Editions sheet records each published format of a title — paperback, hardcover, ePub, audiobook, etc. Each row represents one edition.

Column Notes

Title

MATCH WARNING: This must exactly match the title as entered on the Titles sheet. Use the title only — do not include the subtitle.

ISBN

Import will accept valid ISBN-13s with or without dashes.

Edition Format

To simplify data entry, PubGizmo uses Royalty Groups, which each cover a subset of Edition Formats. The default out-of-the-box definitions are:

Royalty Group Edition Formats Included
Print Paperback, Hardcover
Electronic ePub, PDF, MOBI
Audio Audiobook

You can fully customize Royalty Group and Edition Format names and groupings to suit your press's needs. Your import sheet should reflect your definitions. Please let us know how you plan to set these up before we import your data.

Entries in the Edition Format column must exactly match the names as defined in your PubGizmo instance (or the defaults above, if you are not customizing them).

Units Sold to Last Statement

Royalty rates that include an escalation clause are based on cumulative units sold. If PubGizmo is not receiving historical sales data via import, it needs to know how many copies were previously sold in order to compute escalation correctly.

Fill in this column if both of the following are true:

  1. The applicable contract includes an escalation clause, and
  2. You are not going to import previous sales data.

If you are importing historical sales sheets, leave this column blank — PubGizmo will calculate the cumulative total from those records.

Net Sales to Last Statement

The cumulative net revenue earned by this edition up to and including the last royalty statement completed before onboarding. This is the dollar-value counterpart to Units Sold to Last Statement, and is used alongside it when a contract requires PubGizmo to carry forward a pre-existing royalty balance.

Apply the same rule as above: fill in this column only if both conditions are met (escalation clause applies, and you are not importing historical sales data). Leave blank if you are importing historical sales sheets.

Effective Date (for Units Sold and Net Sales columns)

The date through which the values in the two preceding columns are valid — in other words, the last day of the most recent royalty period completed before onboarding. PubGizmo uses this date to determine where inherited totals end and where its own tracking begins. Format: YYYY-MM-DD.