HomeProducts › Custom Development
CUSTOM DEVELOPMENT

The parts of your operation that are actually yours.

Most of DSD looks the same everywhere. The bits that do not — a rebate scheme, a retailer’s document spec, a warehouse system you are not replacing — we build to your requirement. Scoped with you, quoted against a written spec, delivered into your environment and maintained afterwards.

  • Built to your spec
  • Open REST API
  • Your data, exportable
1ConfigureModules, permissions, templates, pricingno code2IntegrateREST API, 62 groups, on-prem agentyour developers3BuildPartner formats, migrations, reportsus, with you
Built to your requirement Scoped, quoted and delivered to your spec.
An API, not an export The admin app is a client of the same endpoints.
Nothing exposed The on-prem agent calls out; no inbound port.
Maintained, not abandoned Custom work is versioned with the product.

Three ways to fit it to you, in the order to try them

Configuration is free and immediate, integration is your developers’ time, and bespoke work is ours. Working down the list in that order is almost always cheaper.

1Configureyou, in SettingsTurn modules on and off70 permissions, 6 areasYour own document templatesPrice lists, breaks, promotionsStorefront branding2Integrateyour developersREST API, 62 endpoint groupsOpenAPI spec, bearer authScheduled, manual or triggeredOn-prem connector agentThe admin app is a client of it3Buildus, with youTrading-partner formatsA system you are not replacingReports and screens, your shapeMigration off the old systemQuoted against a written gapStart at the top, build at the bottom — we tell you which one you need.

Some of it you can do yourself, today

Part of what people ask us to build is already a permission, a template or a price rule that ships. We will point that out rather than bill you for it — and build whatever is genuinely left.

70separate permissions you can grant or withhold
6module families to switch on or off
Your owninvoice, label, print and email templates
Module switches Run only the parts you use — production, procurement and B2B all turn off.
Roles & permissions Build a role per job, down to the individual action rather than whole screens.
Document templates Your invoice, delivery note, label and email layouts — edited, not requested.
Pricing rules Price lists, quantity breaks, contract prices and promotions, per customer.
Storefront branding Your name and colours on the ordering portal your customers see.
Notifications Choose which events reach whom, rather than everyone getting everything.

How another system reaches the platform

Two roads in, one API at the end of both.

YOUR SIDEORDERPULSECloud systemsERP · WMS · telematicsOn-prem systemsQuickBooks DesktopConnector agentruns inside your networkREST APIOpenAPI · bearer auth62 endpoint groupsthe admin app is a client of itOrdersand estimatesInventorydepot and vanRoutesplan and proofThe agent calls out, so no inbound port is opened into your network.Inbound events land in a staging inbox and replay if a sync fails halfway.
No second-class APIThe admin app is built on the same endpoints your integration uses, so nothing is reachable by us and not by you.
On-prem without a hole in the wallThe connector agent runs inside your network and calls out, so no inbound port is opened.
A failed sync is visibleInbound events stage in an inbox and replay — a sync that dies halfway is queued and shown, not silently lost.
Custom development

What we build for you

Bring us the requirement. We scope it with you, quote it against a written spec, build it into your environment and maintain it alongside the product.

Your specwritten down and agreed before any code
Fixed pricequoted against that spec, not by the hour
Maintainedversioned with the product, not left to rot
Trading-partner formats EDI and DEX documents mapped to the specs your retailers actually send — built per partner, not shipped in the box.
Custom integrations A WMS, a telematics platform, a payments provider or an in-house system that is not going anywhere.
Data migration Customers, items, pricing and history out of the old system and into this one, reconciled before go-live.
Bespoke workflow Rules and approvals that match how you actually run, rather than how the software would prefer you to.
Reports & screens The report the business argues over every month, built once and put in the app.
Event push Today an inbound sync can be triggered on demand; pushing OrderPulse events out to your endpoint is built per engagement.

How an engagement runs

Three steps from your requirement to something running in your business.

1Scope itWe map the ask against what already ships.WHAT YOU GETA written gap list and a price2Build itDelivered into a test environment first.WHAT YOU GETA test window before go-live3Support itVersioned and maintained with the product.WHAT YOU GETUpgrades that keep it workingYour requirement, written down and agreed, before a line of code is written.

Works with the books you already keep

The accounting integrations ship. Anything past them is what this page is for.

Frequently asked questions

Do you have a public API?
Yes. It is a REST API covering customers, items, pricing, orders, invoices, payments, stock and routes, documented with an OpenAPI spec and authenticated with a bearer token. The admin application is itself a client of those same endpoints, so there is no privileged internal API you cannot reach. Talk to us about access for your account.
Do you support EDI and DEX?
Not as a shipped feature. Retailer specs differ enough that a generic implementation tends to fit nobody, so we build the documents and mappings your specific trading partners require as part of an engagement, against the specs they send you.
Can OrderPulse push events to our system?
Today the sync runs on a schedule, on demand, or triggered by an inbound call — and inbound events stage in an inbox so a failure can be replayed rather than lost. Pushing events out to an endpoint of yours is something we build per engagement rather than a switch you turn on.
Will you build a one-off feature for us?
Yes — building to a customer’s requirement is a normal part of what we do, not an exception we grudgingly make. We scope it with you, write the spec down, quote against it and maintain what we build. We will also say plainly when something is already a setting or is on the roadmap, because you should not pay twice for it.
Who owns the result?
Your data and your integrations are yours, and you can export your data at any time. Custom work is versioned and maintained alongside the product, so a platform upgrade does not quietly break what we built for you.
Can we reach a system that is not on the internet?
Yes. A connector agent runs inside your own network and calls out to the platform, which is how the QuickBooks Desktop integration works. Nothing has to be exposed and no inbound port is opened.

Tell us what does not fit.

Bring us the awkward part of your operation. We will tell you honestly whether it needs custom work, or whether it is already a setting you have not found yet.

Request a Demo