The key idea

A reliable catalog import starts with one clearly identified sellable edition per row. Include stable identifiers and the attributes needed to distinguish formats and languages. Keep catalog metadata, production files, sales history and opening inventory as separate inputs. Combining everything into one ambiguous spreadsheet makes errors harder to detect and reverse.

ISBN guidance supports edition identification. The import workflow and quantities here are original operational recommendations. [1]

Prepare the edition record

Use an internal reference or SKU, the relevant ISBN where available, title, author, format and language. Add page count and trim information when the workflow requires them, but do not treat those attributes alone as unique identifiers. Preserve leading zeros and avoid spreadsheet conversions that alter codes. A blank field should remain visibly missing rather than receiving a guessed value. Provide a sample first so mapping problems can be found before the whole catalog is processed.

Validate before committing the import

The importer should report duplicate identifiers, conflicting editions, unsupported values and unclear matches with row references. Decide whether the operation is all or nothing or accepts only valid rows, and tell the user which policy applies. Keep an import reference and a summary of what changed. Repeating the same file should not create duplicate editions. External Amazon candidates should remain subject to the appropriate identity checks rather than being silently accepted as production truth.

Worked example · illustrative assumptions

Imagine a 500 row spreadsheet contains 480 valid editions, ten duplicate rows and ten rows without enough information to distinguish language or binding. A useful import reports those groups clearly. It does not simply announce 500 titles added. The publisher can resolve the twenty questionable rows while the accepted records retain their original source reference. No stock should appear merely because a catalog row was created.

Put it into practice

  • Use one sellable edition per row with stable identifiers.
  • Keep sales, stock and production files separate from metadata import.
  • Review row level errors and verify that repeated imports do not duplicate records.

Watch out for

Do not infer ownership or print permission from the presence of an ISBN in a spreadsheet. Identity mapping and authorization to produce are separate onboarding checks.

Can an import start without every production file?

Yes, if the system separates catalog preparation from print approval. Missing files should block production, not prevent the publisher from organizing the catalog or resolving identifiers.

Sources and further reading

  1. International ISBN Agency: About ISBN. ISBN identifies distinct publication products.

AI assisted editorial content with original planning examples. Source links support the stated source notes; operational suggestions are guidance rather than guarantees. Provider rules and product coverage can change. Editorial approach · BooksAhead.ai connection status.