Dealers still order by model in chat groups? Self-service ordering needs sellable catalog, customer price, and ATP
Distributors post model numbers in the group, sales record orders manually, and the warehouse replies that there is no stock — self-service ordering is not about 'creating a mall page,' but about connecting the salable catalog, customer pricing, credit, and commitment constraints to the same auditable order.
What you'll take away
- Self-order must constrain sellable catalog and customer visibility—no unauthorized models or cost prices
- The order price hits the customer price/promotion price; exceptions require an application, and private price changes within the portal are prohibited.
- Commitments or delivery date reminders should follow the agreed-upon standards; if accuracy cannot be guaranteed, it is better to write 'to be confirmed' rather than pretending the goods are available.
- Credit and minimum order multiples are verified at submission; when the order enters internal confirmation/fulfillment, the status is reported back to the portal
- First, coordinate with core distributors and regularly sold materials, then expand to all product categories; do not open the gateway when price and credit are not stable.
That 'use the last model' in the group chat
On Friday evening, a key distributor posted in the group: 'Following the last enhanced model, send another twenty units, needed next week.' Sales checked the model from the chat record, and when entering it into the internal order, they wrote one suffix incorrectly; the warehouse found no such part number during picking, while the customer had already scheduled the installation team based on 'in stock'.
After the fact, accountability will turn into a three-way blame game: the distributor blames the page (which actually doesn't exist), the sales blames the warehouse, and the warehouse blames the sales dictation. The real problem is—Regular restocking still relies on manual transfer, and during the transfer, there is no point where the catalog, price, credit, and available shipping quantity are all effective at the same time.。
The problem that self-service ordering needs to solve is not 'making customers enjoy clicking,' but to correctly catch wrong orders at the moment of submission and let the team immediately see the same order. A user-friendly page is an experience; overselling and wrong prices are trust—if the latter is broken, no matter how much the former is revised, dealers won't come back.
A portal is not about moving the order form onto a webpage
Many projects understand 'mall' as just the UI: search, add to cart, submit. Missing four things, and the WeChat group will be back within a week:
- Identity = Customer Master DataThe login account corresponds to the settlement entity and organizational authorization, and is not a shared account for the whole family.
- Sellable Catalog Filter: Only authorized models are visible; cost price, unreleased, and diverted-sensitive SKUs are not visible.
- Price hitCustomer price / promotional price is automatically populated and displayed including tax; exceptions require an application, and unit prices cannot be manually changed in the portal.
- Status after submissionInternal confirmation, stocking, shipping, and exceptions need to be reported back; a mall without status is essentially a message board.
Sales proxy entry can be kept for exceptions (customers who won't use the system, urgent verbal orders), but the proxy entry person and the reason must be recorded. Even after going online, everyone still uses proxy entry, it's just an added dual-track, making responsibility even less clear.
Three barriers that must be blocked at the moment of submission
| gate | Stop what? | When it fails, the customer should see |
|---|---|---|
| Minimum Order / Multiple Quantity | Below minimum order, not in whole multiples | Clear rules, not 'submission failed' |
| Credit | Overlimit and overdue strategy triggered | Explain exceeding limits or request for special approval |
| Promised / Delivery Date | No supply or delivery date can be promised | "Delivery date needs to be confirmed" or the quantity that can be promised |
When the credit and settlement entity is not unique, and the credit limit exists in both the ERP and CRM systems, the portal's credit control will only randomly block or randomly allow. Pricing rules are written in the main quotation chain: if the customer price/promotion price has not entered the quotation hit layer, the portal can only display a number that 'looks like a price.' Any disputes must be responded to via WeChat—see the four-layer pricing in the quotation-to-payment section for details.
When what can be promised (ATP/CTP or supply chain visibility) cannot be exact,It’s better to display 'Delivery date needs confirmation' than to write 'In stock' but be unable to ship.. Once overselling occurs, it takes a long time for portal trust to be restored—this is much more costly than a 'page not flashy enough.' Any changes in specifications must be accompanied by edits to the copy to avoid situations where the algorithm inside has been updated, but the portal still displays old promises.
An order is only considered complete once it has entered the internal system.
Self-service submission is not the end. The smallest closed loop is:
Portal submission → Visible in internal order pool → Confirm or reject (reason feedback) → Enter fulfillment (planning/shipping) → Key status back to portal.
Before confirmation, withdrawal and changes are allowed; after confirmation, changes follow the formal process, and delivery dates and credit occupancy are recalculated. The black-box status forces distributors to continue asking in the group 'Where is the order?'—ask too much, and everyone feels WeChat is faster.
Connection with delivery date commitment (OTD): The delivery date prompt on the portal must originate from the same source as the internal commitment standard. If sales give a more aggressive date in the group, being honest on the portal cannot prevent a breach of trust. When direct sales and distribution coexist, the visible range of saleable products and prices should be configured separately to avoid the wrong channel accounts seeing models that are not authorized for them.
Recording on behalf, changing orders, and objections: three side routes most likely to get portals kicked back to WeChat
Recording on behalf. When the customer cannot use the system, it is possible to enter the data on their behalf, but the person entering the data, the reason for doing so, should be recorded, and the customer should be allowed to see the same document in the portal afterward as much as possible. Otherwise, disputes without evidence may arise, such as 'the customer says they didn't place the order' and 'the salesperson says they entered it on behalf.'
Change the order. Changes before confirmation should be simple; after confirmation, changes in quantity, delivery date, or delivery address must go through a formal change process, and it must be clear whether to reallocate credit and whether to recalculate the commitable amount. If you verbally say in the group 'add five more units' without placing an order, the warehouse and finance will always be a step behind.
Objection. Price discrepancies, out-of-stock items, and delivery date changes should be able to leave customer-visible notes on the order status, rather than only in internal remarks. Dealers with weak IT capabilities can use a light link to check the status—the key is to ensure that confirmations and objections are recorded back into the system, rather than creating a separate reconciliation Excel sheet.
The mobile end can only handle browsing and submitting, but status feedback cannot be skipped. A mall without status is essentially still a message board; when the message board is busy, the WeChat group resets.
In the first week, only the range of 'those who can afford to lose' is allowed
On the first day of opening for all categories and all distributors, exceptions are almost always common. A more stable guardrail:
- Only select core distributors and regularly sold SKUs; project-based and custom parts will continue to go through quoting.
- Prices are based on customer prices, and promotional prices must have a validity period if offered.
- Interception copy for insufficient credit is readable, and sales management has clear boundaries for unlocking/special approval.
- After submission, someone must be able to see it in the internal pool; an unattended portal is equivalent to an open message board.
Without a WMS, when short-term inventory visibility is not possible, you can still list items in the catalog and show customer prices, but the delivery time field must honestly be written as 'To Be Confirmed.' Using fake inventory to generate order volume is exchanging channel trust for short-term numbers.
When channel conflicts are undefined (who can see and sell in direct sales/distribution), first determine the scope of visibility and sales before opening the portal. For companies with purely project-based customization and almost no regular sales catalog, the benefits of e-commerce are very low, and there is no need to force a 'digital presence.' Similarly, if pricing and credit master data are not stable, do not open the portal yet—because the portal will amplify dirty prices and false quotas into channel complaints.
For the first week, it is recommended that fixed roles be assigned for duty: sales management should look at exceptions and unlocks, planning or warehousing should check whether the promised capacity has been exaggerated, and finance should verify whether over-credit interception actually occurred. If none of the three pay attention, the portal will be undermined within two weeks by 'shipping first, making up orders later.' The admission standards for expanding product categories can also be fixed: only after complaint rates for wrong types and delivery failures drop to the agreed threshold should the next group of SKUs be added, rather than forcing them according to the launch schedule.
How to connect the main chain in the JEDP-CRM portal
JEDP-CRM extends the customer portal or lightweight collaboration according to scenarios: customers, contacts, credit, and collaboration touchpoints are unified; master data and permission scopes are consistent across multiple sales organizations. If self-service ordering is implemented, acceptance should not just look at whether 'the submit button can be clicked,' but should check: ordering under the distributor account → hitting the customer price → credit control takes effect → internal orders are visible → whether status feedback works correctly.
It shares the same base as the price hierarchy and credit occupancy on the main quotation chain — the portal is a touchpoint, not another price list or another set of inventory lies. In overseas scenarios, if multiple languages are enabled, key buttons and delivery/price fields should be prioritized to prevent cross-border dealers from making incorrect orders due to interface ambiguities. Customized marketplaces can be very attractive, but attractiveness cannot replace auditable orders.
Recommended indicators to monitor: the proportion of self-service orders versus manual entry, complaints about wrong types/prices, instances of overselling or missed delivery commitments through self-service channels, and whether portal status inquiries still largely revert to WeChat. Anti-patterns include: launching the mall while still having everyone manually enter orders, disconnect between catalog and pricing, pages showing stock without standard information, and status never being updated. Using the mall to replace Quote-to-Cash master chain governance is also not advisable—the portal is just an entry point, while contract execution, delivery, and reconciliation still need to follow the same set of facts; if the entry is attractive but the master chain remains broken, channel trust will collapse a second time.
What to do next
Next week, select 5 core distributors and 20 regularly sold materials, and go through the process with a real account: check the visible range after logging in → whether the added-to-cart price is the customer price → whether intentionally exceeding credit or being below the minimum order is blocked → whether it becomes immediately visible internally after submission. At the same time, ask the warehouse: if the page says it can be shipped, can the physical item be sent within the promised time window. If any of the three questions fail, do not expand the product categories; record the drill in the sales and inventory management meeting as the sole basis for deciding whether to open the portal for wider coverage.
- CRM Customer Solution: Customer Portal and Collaboration
Want to apply this in your plant?Resources has matching self-assessments and templates—or book a live demo.
FAQ
Quick answers on this topic—still stuck?Contact
Does self-order replace sales?
No. Regular replenishment is suitable for self-service; complex plans and project-based products still go through opportunity quotation. The goal is to reduce data entry errors, not to eliminate sales.
Whose inventory is authoritative?
The promised specifications must be agreed upon during the plan period (ERP/WMS/ATP, etc.). The portal displays the promised specifications, not arbitrary numbers; do not write 'in stock' when specifications are not determined.
How to manage dealer order changes?
It can be withdrawn or modified before confirmation; after confirmation, changes will follow the change process and may recalculate delivery dates and credit usage. Changes must be recorded to avoid verbal quantity changes in the group chat.
Can self-order go live without WMS?
You can first upload the catalog, customer price, and manually confirm the delivery date, but you must clearly indicate 'delivery date to be confirmed' to avoid being disguised as real-time inventory.
How does this relate to international orders?
Multiple currencies, customs declaration, and delivery schedule rules are more complex and should be listed separately. This topic initially covers the main replenishment path for domestic distributors/portals.