Custom Software Development: End-to-End Delivery from Process Mapping to Go-Live and Operations

Jiding Technology delivers four categories of systems to companies in Suzhou and the Yangtze River Delta: enterprise management software (ERP / CRM / WMS / MES / SCM), mobile applications (mini programs / official accounts / apps), open-source ERP implementation and secondary development, and e-commerce and industry platforms. This page makes it clear: what layers a custom system is built from, what we deliver, how each of the five phases is accepted, where the technology stack and integration boundaries sit, and how a quote is put together. More than 50 systems are in production, and source code and documentation are handed over to the client at delivery.

ARCHITECTURE

Every enterprise system has five layers. First decide which layer belongs to whom

The most common way a custom project loses control is not that the code cannot be written, but that boundaries were never drawn at the start: who supplies the servers, who maintains the interfaces, whether the equipment can actually be read, and who defines the report rules. We split a system into five layers, and the ownership of each layer is written into the requirements document.

① Decision & Insight LayerExecutive cockpitCost & margin analysisCapacity & lead-time forecastQuality & traceability boardMobile approvals② Business Application LayerProcurement & suppliersSales & customer CRMInventory & warehouse WMSProduction & reporting MESFinance & costing③ Platform Capability LayerIdentity & permissionsWorkflow & approval engineReporting & print engineService bus / API gatewayMessaging & scheduled jobs④ Data LayerRDBMS MySQL / SQL ServerTime-series DB TDengineRedis cacheFile & object storageData warehouse / BI⑤ Device & Shop-floor LayerPLC capture OPC UA / ModbusBarcode scanners / RFIDWeighing & metersCameras / vision algorithmsPDA / station tablets↑ Data flows upward · ↓ Rules and commands flow downward
The five layers of a custom system. The highlighted layer is the one budgets most often overlook, yet it decides maintenance cost three years out: the platform capability layer (permissions, workflow, reporting, interfaces).

The business application layer: deciding to buy or build

For procurement, inventory, production, sales and finance, if an off-the-shelf product covers more than 80% of the requirement, buying is cheaper. Custom development only pays off when the gap sits in industry rules such as pricing, approvals and traceability.

The platform capability layer: deciding maintenance cost in year three

If permissions, workflow, reporting and interfaces are rebuilt inside every module, every change in year three has to be made four times. We build them as platform capabilities, so modules simply call them instead of reimplementing them.

The device and shop-floor layer: the uncertainty in every timeline

“Collect data from the equipment” means very different things: a PLC that can be connected directly versus legacy machines that need a gateway and replacement modules can double the schedule. Before we quote, we run a device accessibility survey and turn that uncertainty into a checklist.

Quotes are broken down by layer too: the application layer is priced in person-days per functional module, the platform layer by degree of reuse, and the device layer by number of interfaces and protocol complexity. That is why two projects both called “an ERP” can differ fivefold in price - the difference is not the hourly rate of the developers, but the number of layers and where the boundaries sit. See how the cost breaks down →

SERVICES

Four service lines, each with its own fit and delivery timeline

Identify which category your business falls into before discussing solutions and pricing, and both sides save a great deal of time. The timelines and budget ranges below come from delivered projects; specific projects are assessed item by item.

Service typeWhen to choose itMain modulesTimelineIndicative initial budget
Custom management systems
ERP / CRM / WMS / MES / SCM
Production, pricing or approval workflows have industry-specific rules that off-the-shelf software cannot accommodate; you need integration with production-line equipment, private data and existing systems Procurement, inventory, production, sales, finance, quality traceability, equipment ledger 2–4 months RMB 150k–800k
Mobile application development
Mini programs / official accounts / apps
A mobile entry point for customers or employees: ordering, booking, repair requests, inspections, approvals, data entry Products and orders, membership, form engine, push notifications, WeChat Pay 4–8 weeks RMB 50k–200k
Open-source ERP implementation
Odoo / ERPNext and similar frameworks
Limited budget but fairly standard processes, and you want the source code without being locked in by a vendor Module configuration, custom module development, data migration, permissions and multi-company setup 1–3 months RMB 80k–300k
E-commerce and industry platforms
B2C / B2B / distribution
You need your own storefront and distribution system rather than joining a third-party marketplace, and it must connect with back-office ERP for inventory, pricing and reconciliation Products, orders, payments, logistics, distribution commissions, statements 2–4 months From RMB 200k

Four types of projects we do not take: pure body-shopping billed by person-month, one-off fixed-price jobs with no requirements document, projects that only cover the interface without the back end or the data, and “clone a competitor” projects where the client cannot explain their own business processes. These are not about capability; they are about the odds of success.

MODULES

What really matters in a management system: whether documents flow all the way through

The number of features is not the point. The point is whether a sales order can become a work order, a material issue, a production report, a stock receipt, a shipment and a statement without a break. If even one link is patched with Excel, the data stops being trustworthy and the reports become decoration.

ERP CoreProcurement · Inventory · ProductionSales · Finance · CostingUnified documents and master dataCRMCustomers · Leads · ContractsSCM collaborationSuppliers · Quotes · ReceiptsWMS warehouseBins · Batches · CountsMES shop floorWork orders · Reports · QCE-commerce / Mini programOrders · Members · PaymentsBI dashboardCost · Margin · Lead time
ERP at the core, with surrounding modules deployed independently and synchronizing documents through interfaces: this is the fundamental difference between "one system that grew as a whole" and "several pieces of software bolted together".
ModuleCore documentsMetrics to watch after go-liveThe most common pitfall
Procurement / suppliersRequisition, purchase order, goods receipt, returnOn-time receipt rate, purchase price variance, incoming quality rateOnly results are recorded, not the process, so quotes and receipts never match
Inventory / warehouseStock-in, stock-out, transfer, stock countInventory turnover days, slow-moving value, book-to-physical accuracyBatches and bins are not modeled, so counting is always fixing the books
Production / shop floorWork order, material issue, production report, inspectionPlan attainment, first-pass yield, output per employeeReports are back-filled by team leaders afterwards, so labor hours are inaccurate
Sales / customersQuotation, sales order, delivery note, statementOn-time delivery rate, repeat purchase rate, receivables agingQuotes and orders keep two sets of prices, so margin cannot be calculated
Finance / costingReceivables and payables, expense claims, cost calculationMargin deviation, cost allocation accuracyOperational data is not standardized, so costs are estimated after the fact

Recommended rollout order: master data first (materials, customers, suppliers, warehouses) plus one main flow (order → delivery → statement). Once that runs smoothly, extend into production and costing. Do it the other way round and you usually get stuck on data in month three.

DELIVERY

Five phases, each with something you can sign off on

Software projects usually lose control because "requirements only get thought through after the contract is signed". We confirm requirements before the contract is signed, turn every step into an acceptance point, and tie payments to those points.

STAGE 01Discovery12–3 weeksRequirements specItemized quotePre-contract · FreeSTAGE 02Prototype review21–2 weeksClickable prototypeModule list sign-off20% paymentSTAGE 03Phased development34–10 weeksBiweekly demos + test envInterface & data integration30% paymentSTAGE 04Testing & launch42–3 weeksTest & performance reportsData migration · pilot run30% paymentSTAGE 05Acceptance & handover51–2 weeksSource code · deploy docsTraining · 12-month warranty20% payment
Five phases map to five payment milestones: if a phase fails acceptance, the next phase does not start and the next payment is not made. Phase one (requirements and itemized quote) is delivered before signing - and it is yours even if you do not sign.
PhaseDeliverablesAcceptance criteria (written into the contract)Payment
1 Discovery
Pre-contract
Requirements specification, business process diagrams, module list, itemized quoteYou can restate your business processes from the document, every module has person-days and a unit price, and anything out of scope is listed under "Exclusions"Free of charge
2 Prototype reviewClickable prototype, page list, field and permission tablesMain pages are walked through one by one, the using departments have no "this is not what I asked for", and development starts after sign-off20%
3 Phased developmentA demonstrable build every two weeks, test environment accounts, draft interface documentationEach module passes its acceptance checklist item by item, and issues are resolved in the current period30%
4 Testing and launchTest report, data migration plan and migration records, pilot run recordsFive consecutive working days of pilot operation with no blocking defects, and data reconciled30%
5 Acceptance and handoverSource code, deployment manual, interface documentation, user manuals, training and screen recordingsYour operations team can deploy once independently from the documentation; administrators can add roles and reports on their own20%

RISK CONTROL

Keeping a project on track comes from these four practices, not from overtime

Eighty percent of the cost of custom development is not in writing code, but in repeated clarification and rework. These four rules apply to every project we run, regardless of size.

  • Scope changes go through a written estimate. We price the person-days and schedule impact of a new feature first, and build it only after you confirm - no "finish it now, bill later".
  • The test environment is always accessible. You do not have to wait for a demo day to see progress; what changed yesterday is visible today.
  • Biweekly demos and same-period closure. Issues are resolved in the period they arise instead of piling up for acceptance.
  • Three sign-off points. Written confirmation for requirements, prototype and go-live, so nothing is disowned when a new person takes over.
Jiding Technology development team integrating system interfaces in the test environment
The project team doing pre-launch interface integration: business data reconciliation on the left screen, interface logs on the right (illustrative scene).

TECHNOLOGY

Technology stack and integration: mainstream, documented, and easy to take over

After we deliver, you will still be running this system for five years or more. So we only choose mainstream, well-documented technology and write the deployment manual ourselves - we will not leave you in a situation where only the original vendor can maintain it.

Back end and data

  • Java / Spring Boot, .NET, Node.js, Python - chosen to match your existing ecosystem, never forced into one
  • MySQL / SQL Server / PostgreSQL, relational by default
  • Redis for caching; time-series databases such as TDengine when device data volume is high
  • Sharding and read replicas planned around actual data volume, not over-engineered in advance

Front end and mobile

  • Server-rendered pages: better for search engines and AI crawlers, and a faster first paint
  • Vue / React admin consoles, with virtual scrolling for dense tables and bulk actions
  • Native WeChat mini programs or uni-app, so one codebase covers both mini program and H5
  • Station tablets and PDAs adapted down to 360px, so they work even with gloves on

Industrial and ecosystem integration

  • OPC UA, Modbus TCP/RTU, MQTT, and Siemens / Mitsubishi / Omron PLCs
  • Barcode scanners, RFID, weighing meters, scales, industrial cameras and vision SDKs
  • Document and master data integration with existing ERPs such as Yonyou / Kingdee / SAP
  • WeCom, DingTalk, WeChat Pay, electronic waybills and logistics open platforms
What needs to be integratedCommon approachWhat you need to provideSchedule impact
Existing ERP (Yonyou / Kingdee / SAP)Database views, WebService / REST, intermediate tablesInterface documentation, or a read-only database account+1–3 weeks
Production-line equipment / PLCOPC UA, Modbus, edge gateway pass-throughEquipment list, models, communication manuals+2–6 weeks (including on-site commissioning)
WeChat ecosystemMini program and official account APIs, WeCom, WeChat PayA verified entity, merchant number, certificates+3–5 days
Logistics / electronic waybillsCourier open platform APIsMonthly settlement account, keys, shipping rules+3–7 days
Single sign-onLDAP / OAuth2 / CASDomain controller or identity platform details+3–7 days

Deployment, pick one of three: on-premises servers (data never leaves your intranet), public cloud (Alibaba Cloud / Tencent Cloud, with effortless elasticity and backups), or hybrid (database on-premises, application in the cloud). We have ready-made deployment scripts and operations manuals for all three.

DELIVERABLES

What you receive at acceptance: eight categories, more than twenty documents

"We hand over the source code" is not a slogan - it is the checklist below. At the acceptance meeting we hand over each item one by one, and acceptance is not complete until every item is delivered.

CategorySpecific deliverablesWhat problem it solves
RequirementsRequirements specification, business process diagrams, module list, scope and exclusions documentThe basis for acceptance, and the handover material if the team changes in future
DesignInteractive prototype, UI designs, icon and sliced asset source filesPage-level confirmation, reducing "we only realized it was wrong after it was built"
CodeFront-end, back-end, database scripts, scheduled jobs and configuration filesComplete source code, unencrypted, without license restrictions or platform lock-in
InterfacesInterface documentation (OpenAPI), third-party integration notes, error code tablesNo need to ask the original vendor when integrating with ERP, devices, payments or logistics
DeploymentDeployment manual, environment checklist, initialization scripts, backup and restore proceduresYour operations team can deploy once independently
OperationsMonitoring checklist, logging standards, troubleshooting manualWhen something goes wrong after go-live, you know where to look first
TrainingUser manuals by role, administrator manual, training screen recordingsThe system still has people who can use it after staff turnover
LegalSource code and IP ownership clauses, warranty period and response times (SLA)Copyright stays with the client, who can migrate or change maintenance teams freely

INDUSTRIES

Typical industry scenarios: six lines of business we have delivered

The value of industry experience is not what the interface looks like, but knowing what the documents, batches, traceability and settlement rules of that industry look like.

Equipment and machinery manufacturing

Engineer-to-order design, non-standard quoting, multi-version BOMs, outsourced operations, project progress and cost allocation. The hard part is "a different price for every order" and designing while producing.

Automotive parts

PPAP and batch traceability, supplier portals, kanban pull systems, tooling and fixture management, and integration with customer demand plans.

Pharmaceuticals and GSP distribution

First-time supplier and product qualification review, batch number and expiry management, temperature and humidity record retention, accompanying delivery notes and drug regulatory interfaces.

Food and agricultural processing

Purchase weighing and farmer settlement, grading and sorting, batch traceability, shelf life and cold chain, production-line data dashboards.

Electronics assembly

SMT feeder error-proofing, work order and feeder slot binding, test data acquisition, defect repair and traceability, piece-rate wages.

Trading and distribution

Multiple warehouses and organizations, pricing and rebate policies, dealer ordering mini programs, field sales visits, reconciliation and credit terms.

COMPARISON

All custom work, but how do three kinds of suppliers differ

DimensionLow-cost outsourcing teamsLarge software companiesJiding Technology
How they quoteA single lump sum, no breakdownProduct license plus implementation person-days, with a long list of configuration itemsModules × person-days × unit price, with a breakdown you can check item by item
Requirements phaseWork starts after a verbal confirmationDriven by pre-sales, delivered by implementation consultantsRequirements spec and itemized quote before signing - yours even if you do not sign
Source code ownershipOften withheld, or encrypted and license-restrictedPlatform lock-in, with secondary development controlled by the vendorAll source code and documentation delivered, copyright stays with the client
CommunicationOne salesperson for the whole project, no technical staff in sightMultiple layers of intermediaries, requirements degrade in transitDirect contact with the technical lead, with on-site discovery
Change requestsPrices creep up as work proceeds, or changes are simply refusedA long change process with additional chargesWritten estimate, implemented after confirmation, recorded in a change order
After go-liveImpossible to reachAnnual maintenance contracts, with response times by severity12-month warranty plus optional annual support, with the SLA written into the contract

CASE STUDY

Related case studies

Client names can be anonymized, but the industry, scale and approach are retained. The cases below are directly related to the services described on this page.

Curated mall app for a health-retail brand
EC AppE-commerce platform, distribution platform

Curated mall app for a health-retail brand

A shopping app for a health-retail brand: self-operated quality assurance, curated and daily-plus zo...

View case study →
Smart fire-safety platform for residential communities
System Integration OMSmart fire protection, community fire protection IoT

Smart fire-safety platform for residential communities

A fire-safety management platform for property managers and district fire supervision: admin console...

View case study →
Intelligent finance & tax management platform
EMSSmart finance and taxation, agency bookkeeping

Intelligent finance & tax management platform

An all-in-one internal management platform for a bookkeeping and fiscal-service company: customer pi...

View case study →

View all case studies (filterable by type) →

FAQ

Frequently asked questions

What deliverables are included in the custom development of mini programs?

Requirements specification, UI design draft, mini-program front-end and back-end source code, management backend, interface documentation, deployment documentation, and operation manual, as well as completing a formal online launch and backend training. Upon acceptance, all deliverables will be handed over to Party A, with copyright belonging to Party A.

What is the difference between customizing and developing an ERP system and purchasing an off-the-shelf ERP system?

Ready-made ERP systems are suitable for standard financial purchase-sale-stock processes, with fast implementation and low cost. When an enterprise's production, pricing, and approval processes differ significantly from standard products, or when integration with production line equipment and private data is required, the labor costs incurred by adapting processes to the software will continue to accumulate. In such cases, the total cost of customizing or conducting secondary development on open-source ERP systems may actually be lower. We can help you evaluate both options for free.

Got a requirement you cannot quite articulate? Start with a requirements document

A 60-minute process review is enough for us to translate your pain points into modules, person-days and an itemized quote you can sign.

1.173981s