Custom DashNex Modules Explained: Bookings, Portals and Invoices

A DashNex module is a packaged add-on that plugs new pages, data, admin screens and automations straight into your DashNex app. Start with the built-in tools. Wait for a marketplace module if one is close and your need can wait. Commission a custom module only when the workflow is central to how your business earns money.

What a DashNex module is, in plain words#

Think of your DashNex app as a building, and modules as the rooms. Some rooms come finished: contacts, email, products, offers, checkouts, the member portal and the AI support chat. You can add more rooms later without knocking down walls.

The DashNex documentation puts it simply: "Modules are the building blocks of your WebApp." Even the core business tools are modules. That is why adding a new one feels native rather than bolted on.

A module is not a widget pasted into a page. It is real code that shares your app's customers, data and payments. The DashNex developer page says a module "plugs straight into the app", with access to its pages, data, customers and payments.

What a module can contain#

Here is what a module can add, with a business example for each part.

The event part matters most for owners. When a customer buys, signs up or gets a tag, any module can respond. That is how one purchase can update a contact, open a portal and start an email sequence without any outside automation tool.

How modules are installed and updated#

Modules are shipped as versioned packages and installed into your app. The DashNex developer page says builders can set "a one-time, monthly or annual price" and let businesses install with one click. Updates arrive as new versions, so you are not editing live code by hand.

What comes built in already#

Before you look at add-ons, check what you already have. The DashNex docs list products, offers, checkouts, coupons, contacts and opt-in forms. They also list email broadcasts, automations, an inbox, a pages manager, a media library, instraCHAT and MCP access. The DashNex pricing page says these business tools "come installed with every app at no charge."

That covers a lot. Most small businesses we meet can run sales, email and support on the built-ins alone. Our DashNex review walks through each built-in tool and where it stops.

Three modules we have in development#

We are building three modules for the DashNex module marketplace. They are in development, so details will change before release. We describe them here as examples of what a module makes possible, not as product promises.

A bookings module#

Service businesses live on their calendars. Today, many pay a separate booking tool, then copy names into their CRM by hand.

A bookings module is designed to keep the whole flow inside DashNex. A customer picks a service and a time on your domain, and a deposit can go through your existing checkout. The booking lands on the customer's contact record, and scheduled jobs send reminders. Staff see their day in an admin calendar.

An agency client portal#

Agencies juggle shared drives, email threads and status calls for every client. A client portal module gives each client one signed-in place on the agency's own domain.

The idea is simple. A client logs in and sees their projects, files, approvals and invoices. The agency manages it all from admin screens. Because it runs on DashNex, a new purchase can open a client's workspace automatically through an event listener.

A quotes and invoices module#

DashNex already handles invoices for offers and subscriptions. What many service businesses lack is the step before payment: a quote the client can review and accept.

A quotes and invoices module is meant to close that gap. You build a quote from line items, send it, and the client accepts online. The accepted quote can become an invoice and a payment link. Every step sits on the same contact record.

Use built-in, wait, or build your own#

This is the decision most DashNex owners face. Use this table as a first pass, then talk it through with whoever builds for you.

Two warning signs suggest a custom module is premature. The first is that you cannot describe the workflow in five steps. The second is that nobody on your team does the task by hand today. Fix the process first, then automate it.

How a custom DashNex module gets built#

Here is how we run a custom module project. It follows the same four stages as all our services, with module-specific steps inside.

1. Discover. We map the workflow, the people who touch it and the tools it replaces.
2. Scope. We agree on a fixed scope, quoted before any build starts.
3. Design the data. We define the tables, the admin screens and which app events the module listens to.
4. Build in weekly iterations. You see working screens each week, not a big reveal at the end.
5. Test with real scenarios. We try the awkward cases too, such as failed payments and double bookings.
6. Deploy and hand over. The module goes live in your app, and you get access and documentation.
7. Evolve. New features ship as new versions, without breaking what already works.

Step 3 is where most projects are won or lost. A clear data model makes every later feature cheaper to add.

What a custom module costs to run#

A custom module runs inside your own DashNex app. It uses the same hosting, which DashNex bills at Cloudflare's rates through usage credits. There is no separate subscription for the module itself.

Build cost depends on scope, so we do not publish a price list. Every project is fixed scope, quoted. The aim is a one-off build that replaces a recurring bill, which is the same idea behind our small business SaaS audit.

Who owns the code#

DashNex says each app comes with its full source code that you can change. For custom modules, we write ownership into the scope before work begins. On our projects, the client owns the code, content, configuration and data.

You are reading one right now#

This blog runs on a DashNex module we built. Categories, call-to-action cards, the FAQ below and the structured data search engines read all come from that module. It lives in the same app as the rest of our site, with no separate blogging platform.

We mention it because it shows the point better than any diagram. A module can be large enough to feel like its own product, while sharing your app's domain, design and data.

Common mistakes when commissioning a module#

We see the same few mistakes again and again. Avoid them and your project will go faster.

• Rebuilding a built-in tool. Check the docs first. DashNex may already do the job.
• Starting with every feature. Ship the core workflow, use it for a month, then add the rest.
• Skipping the events. The value of a module often comes from what it triggers elsewhere in the app.
• No owner on your side. Someone must test each weekly build and make decisions.
• Treating it as a website job. A module is software. Plan for versions, not a one-time launch.

Thinking bigger than a module? Our guide to building a SaaS without coding covers when a full product makes more sense.

FAQ#

What are DashNex modules?#

DashNex modules are the building blocks of a DashNex app. Each one can add customer pages, admin screens, database tables, API endpoints, event listeners and scheduled jobs. Contacts, email, checkouts and AI support chat come preinstalled as modules. You can add marketplace modules or commission custom ones for workflows the built-ins do not cover.

Can DashNex handle bookings?#

Not as a built-in tool in the DashNex docs we checked. Bookings need a module. We have a bookings module in development for the DashNex module marketplace. If you need bookings now, a custom module can connect scheduling to your existing contacts, checkout and email so everything stays on one record.

Does DashNex have a client portal?#

DashNex includes secure customer accounts and a member portal, so buyers can sign in and reach what they bought. A full agency client portal, with projects, files and approvals per client, needs a module. We have one in development for the marketplace, and the same idea can be built as a custom module today.

How much does a custom DashNex module cost?#

It depends on scope: the number of screens, the data model and which app events it uses. We quote every project as a fixed scope, so you know the price before work starts. Once live, the module runs on your app's usage-based hosting, with no separate monthly subscription for the module itself.

Should I wait for a marketplace module or build my own?#

Wait if the feature is common, a module is in development, and you can manage without it for now. Build your own if the workflow sets your business apart, or if you are paying a monthly tool just to fill the gap. Our decision table above walks through the most common situations.