What is a journal management system? Choosing between OJS, national platforms and commercial systems

When an editor goes looking for journal software, the number of names outstrips the number of options: journal management system, manuscript tracking system, manuscript management system, electronic journal system, peer-review platform, sometimes just journal software. Editors search for all of them, because nobody tells them which term is correct — and they are right to: the terms largely describe the same category.

The proliferation is not an innocent matter of vocabulary. Because the category’s boundaries are vague, a single search returns tools of wildly different weight side by side: a national public infrastructure here, a standalone package installed for one journal there, and elsewhere the journal module of a system that runs an entire press. This piece tries to define the category first, then to place the realistic options honestly.

The core: what any such system must cover

Whatever the label, the essential work is well defined:

1. Submission. The author delivers the manuscript, its metadata and supporting files online; every resubmission is preserved as a distinct version.
2. Desk screening and editorial flow. Completeness checks, scope fit, section editor assignment, desk rejection.
3. Peer review. Reviewer invitation, accept/decline tracking, review forms, reminders, backup reviewers — with anonymity enforced by the system rather than by good manners.
4. Decisions and revision rounds. Decisions recorded with their reasoning; revision rounds living under the same record.
5. Issues and publication. Table-of-contents ordering, proofing rounds, issue release, online-first support.
6. Metadata and permanent addresses. A durable page per article, clean metadata, DOI registration, output that indexes and search engines can actually read.
7. Records and reporting. Who did what and when; turnaround time, acceptance rate, reviewer load. The process documentation that index applications demand is simply the by-product of this record — we wrote about that here.

A tool that fails these seven is outside the category no matter what its brochure says. A tool that meets them is inside it — whether it is a hosted national platform or an OJS instance on your own server.

The four realistic options

1. A national or consortial hosting platform

In Türkiye this is DergiPark, run by TÜBİTAK ULAKBİM: free hosting, submission-to-publication workflow and DOI provision for Turkish academic journals. Many countries have an equivalent.

The strength is undeniable — publishing on trusted public infrastructure with no budget and no server. The limitation comes from the same place: it is a shared platform, so the room for an institution to impose its own workflow, look and integrations is narrow. We looked at exactly where that line falls in DergiPark: what it does and what it doesn’t.

2. OJS (Open Journal Systems)

OJS is the most widely used open-source journal software in the world; PKP’s own data puts it near 58,000 journals. No licence fee, high flexibility, a large international ecosystem.

What is free is the licence, not the operation. Installation, upgrades, backups, plugin compatibility and security patches are somebody’s job; where the institution lacks that capacity, a service provider takes it on. The question to ask is not “is it free” but “who upgrades this instance five years from now.”

3. Commercial journal and manuscript systems

There are dedicated commercial systems in most markets, plus the long-established international platforms used by large publishers. Their shared promise is to take OJS’s operational burden off your hands and add support in your own language.

The thing to watch here is scope: the system runs the journal’s process. The institution’s book publishing, royalty accounting, inventory and sales sit outside it and get handed to other programs.

4. Publishing management systems

The fourth option moves the question up a floor: systems that treat a journal not as a separate program but as one work type in the institution’s publishing life. Journals and articles live under the same record model as books and book chapters, and after publication the sales, stock and accounting side continues in the same system. We defined the category in what is a publishing management system.

For a society that publishes a single journal this is overkill. For a university press that publishes both journals and books, the other three all fall short: even with the journal side solved, book workflows, royalties and sales still live in email and spreadsheets.

Seven questions to ask before deciding

Feature lists all look alike, so the distinctions surface here:

1. Are you running a journal or a press? Journal only — keep the scope tight. Books too, and two separate systems will produce two separate versions of the truth by month six.
2. How much of the workflow is yours? Who configures review steps, voting rules and required fields — the institution, the vendor, or nobody?
3. Who owns anonymity? Is double-blind review enforced by the system, or delegated to a warning about checking your file names?
4. How do external reviewers take part? If an invited expert hits a “create an account first” step, your reviewer-recruitment problem grows for a purely technical reason.
5. Can the process record be reported? When an index or an audit asks, does the file fall out of the process — or does someone assemble it by hand?
6. Is the metadata sound? Are article pages real indexable pages, or a list of PDFs? Most of a journal’s visibility is won or lost right here.
7. Who carries the upkeep? Setup is paid once; upgrades, backups and support are paid every year. If the second has no named owner, your price comparison is incomplete.

The right question is not “which is best”

These four options compete less than they complement. For a society with one journal, a hosted national platform is more than enough; for a press running ten journals and forty books a year, none of them suffices alone. What decides the matter is not the feature list but the breadth of the institution’s publishing life.

A quick, useful test: write down every publishing task you handled in the last year outside journal workflow — book submissions, author contracts, print jobs, sales. If the list is short, a journal-focused system is the right answer. If it is long, the thing you are looking for is not a journal management system.

Nasirus was built for that second case: journal and article workflows run in the same system as books and chapters. Have a look at the modules, or book a demo and we will walk through your own journal’s workflow together.