Appearance
ERP Jobs and D4 Connect
Many Riv merchants run D4 Connect for their online shop. ERP Jobs is an optional workshop module on the same ERPNext back office. This page explains what is shared, what is separate, and how your team should think about day-to-day tools.
Two products, one back office (when both enabled)
| D4 Connect | ERP Jobs | |
|---|---|---|
| Purpose | Online storefront, cart, checkout, merchant dashboard | In-shop repair job cards and workshop workflow |
| Who uses it | Shop owner, online fulfilment staff | Front desk, workshop manager, bench technicians |
| Primary sign-in | Merchant dashboard (email invite) | ERPNext Desk (Jobs workspace) |
| Customer-facing | Your public website | Booking emails, quotations, ready-for-collection notices |
| Record type | Web sales orders (via checkout) | Job documents |
You can use D4 Connect without ERP Jobs. ERP Jobs is for repair and service workshops — electronics repair, appliance service, trade benches.
What is shared
When both run on your ERPNext site:
| Shared data | How it helps |
|---|---|
| Items | Parts you sell online can be issued to repair jobs from stock |
| Customers | One customer record — desk sees the same party as online orders |
| Stock | Warehouse movements from jobs and from online fulfilment update the same inventory (when configured) |
| Invoices | Standard sales invoices — accounts sees one AR picture |
Your merchant dashboard changes to products and stock still flow to ERP — workshop staff see those items in Desk.
What stays separate
| D4 Connect | ERP Jobs |
|---|---|
| Online cart and checkout | No cart — intake at front desk |
| Convex order tracking and Paystack web checkout | Assessment and repair invoices in Desk |
| Merchant dashboard fulfilment queues | Jobs reports and workflow buttons |
| Product pages on your website | Job status is not on the storefront in v1 |
An online order does not create a repair job. A repair job does not appear in the merchant Orders list. Train staff on which screen to open.
Which tool for which task?
| I need to… | Use |
|---|---|
| Add a product to the website | Merchant dashboard — Products |
| Fulfil an online order | Merchant dashboard — Orders |
| Book a repair walk-in | ERP Jobs — create Job |
| Issue parts to a bench repair | ERP Jobs — stock issue or material request |
| Run warehouse accounting reports | Back-office desk |
| Track repair from booking to collection | ERP Jobs — repair workflow |
Good to know
The back-office desk is general ERPNext for warehouse and accounts. ERP Jobs is a dedicated Jobs workspace for repair workflow — not the same menus as generic Desk, though both are ERPNext.
Plans and provisioning
ERP Jobs is typically enabled on dedicated ERP sites (medium/large workshops), not the default small-shop pool-only plan. Your D4 contact confirms whether Jobs is included.
Listing-only storefronts (catalog without checkout) can still run Jobs on the ERP side — common during phased go-live.
Customer experience today
- Shoppers browse and buy on your D4 website.
- Repair customers get booking slips, quotation emails, and ready notices from ERP Jobs.
- There is no customer portal for live job tracking in v1 — staff communicate by phone, email, or WhatsApp.
For managers
| Topic | Guidance |
|---|---|
| Stock conflicts | Coordinate parts warehouse between online fulfilment and bench |
| Pricing | Online prices (Item Price) may differ from quotation lines on jobs — quotations are negotiable per repair |
| Staff training | Dashboard team vs workshop team — minimal overlap except shared stock |
| Reporting | Online GMV in D4; workshop throughput in Jobs reports |
Next steps
- ERP Jobs overview — module introduction
- Getting started — first job
- D4 Connect overview — online shop
- Back-office desk — when to use general Desk vs Jobs
Riv staff
Architecture and tenancy: internal ERP Jobs docs · D4 ERPNext integration