These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Publishing House ERP
- Features
- Print editions
Print editions
Keep ISBN and edition details connected to the manuscript they describe.
OverviewPrint Editions List×
Publishing House ERP · Print editions
New
Print Editions List
Print editions
| ISBN | Edition number | Print quantity | Release date | Manuscript | |
|---|---|---|---|---|---|
| ISB-171 | 710 | 50 | 25 Oct | MNS-2879 | |
| ISB-336 | 140 | 300 | 07 Oct | MNS-7905 | |
| ISB-440 | 90 | 50 | 25 Oct | MNS-2851 | |
| ISB-487 | 350 | 200 | 20 Oct | MNS-4050 | |
| ISB-235 | 30 | 250 | 20 Oct | MNS-3427 |
6 of 6 records
ISB-171Print editions · PE-69237
Edition number710
Print quantity50
Release date25 Oct
ManuscriptMNS-2879
What you can do
Record the edition
A print edition ties an ISBN, edition number, print quantity and release date to one manuscript. This gives the Production Lead a single place to read the edition facts beside the manuscript title and editorial status. An edition record describes the planned or recorded print edition; the quantity field should be used consistently by the team so a report does not mix estimates with actual print results.
How the work is organized
- ISBN convention. Agree who allocates the ISBN and how it is checked before entry.
- Edition numbering. Agree how revised editions are numbered for the same manuscript.
- Quantity meaning. Agree whether the entered print quantity is the authorized run or a later physical result.
What to agree during setup
Start with one real title and name the person who is responsible for the record. Decide who can revise dates or statuses, and when a change needs another person’s review. Check each actual project, manuscript, content or person reference before using that record in a handoff. The agreed practice should be visible in the record, not held only in an email thread.
For each handoff, identify the person expected to act next. Check that their user and People record are connected before relying on an approval decision. Keep the source attachment or agreement with the relevant record when the decision depends on it. This makes the working lists useful during a busy production week.
Check the handoff on an actual case
Take a manuscript that has completed editorial review and is entering production. The Production Lead checks the manuscript reference, enters its ISBN, edition number, print quantity and release date, then reviews the edition against earlier entries for the same manuscript. Compare later editions with the existing ISBN and edition number before entry. If the release date changes, have the Production Lead correct the edition record and review the updated facts with the team. The Managing Editor can read the manuscript history while the Publishing Director sees which edition belongs to the title. The edition record should be checked against the physical printer or distributor handoff when those teams confirm actual production.
Before expanding to other titles, ask the people named above to walk through this case in the app. They should be able to point to the current record, explain the next decision and find the owner without reconstructing the history from messages.
What your team sees
- Print Editions List — Edition identifiers, quantity and release date alongside the linked manuscript.
- Manuscripts Awaiting Review — Editorial status before an edition enters production planning.
Follow the work through
See the related process and the data model for the records behind this handoff.
What it keeps track of
Data model- Print editions
- Print editions and ISBN records for manuscripts
- Manuscripts
- Submitted manuscripts under editorial review
- People
- Staff and contributors of the publishing house
Who uses it
Permissions- Production Lead
- Records edition details.
- Managing Editor
- Owns the manuscript decision.
- Publishing Director
- Reviews release timing.
Set up Publishing House ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.