Here is the objection that kills more university press D2C initiatives than any budget constraint or strategic disagreement: "We do not have the IT staff to build and maintain an ebook store."
It is a reasonable concern. The typical mid-size university press — the sweet spot of 10-50 employees managing 50-500 titles — has a marketing coordinator, an editorial team, a production manager, and maybe a digital operations specialist. It does not have a web developer, a DevOps engineer, or a DRM integration specialist on payroll.
Five years ago, this was a genuine barrier. Building a D2C ebook store meant commissioning custom development, integrating third-party DRM systems, setting up payment gateways, building mobile reading experiences, and maintaining all of it indefinitely. The total cost could easily reach $50,000-$150,000 for initial development, plus $20,000-$40,000 annually in maintenance and hosting.
That barrier no longer exists. Modern publishing platforms — specifically those designed for university presses and academic publishers — have reduced the technical requirements to near zero. This guide walks through the actual process of launching a university press ebook store, step by step, with realistic timelines and no assumed technical expertise.
What You Actually Need (And What You Do Not)
Before diving into the process, let us clear up what is and is not required:
You need:
- Your catalog metadata in ONIX format (you almost certainly already produce this for your distributors)
- EPUB and/or PDF files of your ebook titles
- A Stripe or compatible payment processor account (setup takes 1-2 business days)
- Your press's logo, brand colors, and basic style guidelines
- A person responsible for the store (1-2 hours per week for ongoing management)
You do not need:
- A web developer or IT team
- Server infrastructure or hosting setup
- DRM licensing agreements with third-party vendors
- Mobile app development expertise
- Custom code of any kind
If you can manage your titles in an ONIX feed and upload files to a web interface, you have the technical skills required.
The 30-60 Day Launch Timeline
Here is a realistic timeline for launching a university press ebook store on a platform like Publica.la. This assumes one person dedicating approximately 5-8 hours per week to the project alongside their regular responsibilities.
Week 1-2: Platform Setup and Catalog Import
Day 1-3: Account setup. Create your publisher account, configure your press's branding (logo, colors, typography), and set up your custom domain or subdomain (e.g., store.yourpress.edu). This is a configuration interface, not code — think Squarespace or Shopify, not WordPress with custom PHP.
Day 4-7: Catalog import. Upload your ONIX feed. The platform maps your existing metadata — titles, authors, ISBNs, descriptions, subject categories, prices — directly into your store catalog. For a press with 200 titles, this typically takes 1-2 hours of active work plus processing time. Review the imported data for any mapping issues, fix edge cases, and approve.
Day 8-14: Content upload. Upload your EPUB and PDF files for each title. If you already have DRM-free files (which most presses do for their digital distributor feeds), these can be batch-uploaded. The platform applies its built-in DRM automatically — no separate DRM vendor integration required.
Week 3-4: Storefront Configuration
Collections and categories. Organize your catalog into browsable collections: by subject, by series, by "new releases," by "bestsellers," by "award winners." This is editorial curation, not technical work — and it is where your press's expertise actually shines. No algorithm knows your catalog better than you do.
Pricing and currencies. Set prices for each title (or import them from your ONIX feed). Configure multi-currency support if you want to sell internationally — the platform handles currency conversion, local payment methods, and tax calculation automatically.
Payment processing. Connect your Stripe account. This is a one-time configuration that takes 15-20 minutes. Once connected, the platform handles all transaction processing, including tax collection, receipt generation, and payout scheduling.
Storefront design. Customize your store's appearance using the platform's design tools. Choose layouts for your homepage, category pages, and book detail pages. Add your press's mission statement, about page, and contact information. Again — this is configuration, not development.
Week 5-6: Reader App Branding
This is where platform choice matters most. With Publica.la, your readers do not download a generic reading app — they download your press's branded app on iOS, Android, macOS, and Windows. The app carries your press's name, logo, and visual identity.
App branding. Provide your logo, icon, and brand colors. The platform generates your branded reader apps for all platforms. No app development skills required. No separate App Store developer accounts needed — Publica.la handles the publishing and updates.
Reading experience. The reader app supports EPUB, PDF, and audiobook formats with built-in DRM, offline reading, annotations, bookmarks, and cross-device sync. Your readers get a modern, polished reading experience under your brand — not a third-party app that dilutes your identity.
Week 7-8: Testing and Launch
Internal testing. Share the store with your team for testing. Place test orders, verify the purchase and download flow, check the reading experience across devices, and review the storefront on mobile and desktop. Fix any catalog issues (missing cover images, incorrect prices, incomplete metadata).
Soft launch. Open the store to a small audience — your email list, your social media followers, or a specific department's faculty. Monitor for any issues and gather initial feedback.
Full launch. Announce the store to your full audience. Add a link to your press's main website. Include the store URL in your email signatures, book marketing materials, and conference handouts. Share across your author networks.
The Real-World Comparison: Publica.la vs. Alternatives
University presses evaluating D2C options typically encounter three categories of solutions:
| Solution | What It Offers | What It Lacks | Typical Cost |
|---|---|---|---|
| Supadu | Website + shopping cart integration | No reader apps, no built-in DRM, no ebook delivery platform | $220-3,500/mo + $15K+ initial build |
| Fulcrum (Michigan) | Open-source hosting for OA monographs | No e-commerce, no D2C sales, no reader apps | Free (but no revenue generation) |
| Manifold (Minnesota/CUNY) | Open-source reading platform for iterative publishing | No retail sales, no DRM, no mobile apps | Free (but no revenue generation) |
| Publica.la | D2C store + branded reader apps + DRM + analytics + international bookshop network | Not a website CMS (complements your existing site) | Platform fee based on catalog size |
Supadu solves the website problem but not the ebook delivery problem — you still need a separate reading platform, DRM solution, and mobile apps. Fulcrum and Manifold are valuable Open Access tools but are not designed for revenue-generating D2C sales. Publica.la is the only option that provides the complete D2C stack: storefront, DRM, reader apps, payment processing, and analytics in a single integrated platform.
What Ongoing Management Looks Like
After launch, maintaining your ebook store requires minimal ongoing effort:
- Adding new titles: Upload EPUB/PDF + metadata when new books are released (15-30 minutes per title)
- Updating catalog: Sync your ONIX feed periodically to update prices, metadata, or availability (automated or semi-automated)
- Running promotions: Create seasonal sales, conference discounts, or course adoption offers through the platform's promotion tools (30-60 minutes per campaign)
- Reviewing analytics: Check sales performance, reader engagement, and store traffic weekly (15-30 minutes)
Total ongoing time commitment: 2-4 hours per week, easily managed by your existing marketing or digital operations staff alongside their other responsibilities.
Addressing the Common Objections
"Our university's IT department needs to approve new platforms." Fair point. Publica.la is a SaaS platform — it runs on its own infrastructure, not your university's servers. There is nothing to install, no server requirements, and no integration with university systems required (though SSO integration is available if desired). The IT review is typically minimal.
"We are worried about cannibalizing our Amazon sales." D2C revenue is largely incremental. The readers who buy directly from your store are typically those who already know your press — faculty, conference attendees, email subscribers — not casual Amazon browsers. For the full analysis, see our article on the true cost of Amazon dependency.
"We only have 50-100 titles. Is it worth it?" Yes. A focused catalog is actually easier to launch and manage than a massive one, and the per-title revenue impact of D2C margins (80-90% vs. 35% on Amazon) is significant even at modest sales volumes.
"Our readers prefer print." Some do, and print will remain part of your mix. But the digital share of academic book sales grows every year, and faculty course adoption is increasingly digital. A D2C store that offers both ebooks and audiobooks captures the growing digital demand while your print distribution continues unchanged.
Start With What You Have
You do not need to digitize your entire backlist to launch. Start with your most recent 2-3 years of titles, your strongest sellers, and your course adoption candidates. Get the store live, learn from the data, and expand the catalog over time.
The presses that launch in 2026 with 50-100 titles and grow from there will be in a fundamentally stronger position than those that wait for the "perfect moment" to launch with a complete catalog. The perfect moment is the one you choose.
Ready to launch your store? Explore Publica.la's university press solution, or schedule a walkthrough to see the platform in action with your catalog.
