Review supplier requests linked to Helpdesk
Choose Support & requests. Review request reference, linked ticket number, category, subject and state. Supplier requests route to the native Helpdesk Supplier Support queue.
Before you start
Use your authorized ERP account and the correct company. These screenshots use fictional staging records. Replace the example quantities, dates, warehouses and values with your approved business information. Submission affects the relevant workflow or stock ledger; review the draft first.
Addresses used in this tutorial
ERP_URL is your organization’s ERP address. ACADEMY_URL is the Academy base address: staging uses https://erpstaging.nexcommand.ai/academy; production uses https://academy.nexcommand.ai. Saved record IDs and temporary draft IDs differ between installations. Course IDs and element IDs in the example are not portable to another installation.
Supplier Portal address and preview
SUPPLIER_URL is your organization’s supplier portal. Production uses https://supplier.nexcommand.ai directly; these staging screenshots use https://erpstaging.nexcommand.ai/supplier. The screenshots are labelled staff preview and contain synthetic suppliers. Preview does not grant supplier access, and category saving is disabled. Use an approved supplier account for your own records.
Step-by-step instructions
Open supplier support
Choose Support & requests. Review request reference, linked ticket number, category, subject and state. Supplier requests route to the native Helpdesk Supplier Support queue.
- Example / selection
- NC-SREQ-00021; ticket #0022; Open
- Expected result
- The ERP request and Helpdesk ticket are linked.
{SUPPLIER_URL}/
Prepare a clear request
Choose Category. Enter Subject and Details. Select Related document type and the specific Document when the issue concerns an RFQ, order, receipt or invoice. Include your reference and requested response deadline when useful. Submit only after reviewing the actual request and recipients.
- Example / selection
- Order inquiry linked to the affected purchase order
- Expected result
- The request fields explain the issue and its context.
{SUPPLIER_URL}/
Review the conversation
Choose View Ticket on an existing request. Read state and conversation, including linked order context. Enter a follow-up only when you intend to send it. The pictured synthetic ticket already contains a follow-up.
- Example / selection
- Ticket #0022
- Expected result
- The supplier can track the existing request.
{SUPPLIER_URL}/
Route profile and bank corrections appropriately
Open Company profile to review supplier information. Request corrections through Support. Bank changes require separate Finance verification and cannot directly change payment instructions through this portal.
- Example / selection
- Company corrections through Support
- Expected result
- Sensitive payment changes remain subject to review.
{SUPPLIER_URL}/
Verified result
Existing synthetic ERP request and Helpdesk ticket references were verified in staff preview. The request form and existing conversation were inspected. No new request, follow-up, bank change or notification was sent during this walkthrough.
Troubleshooting
Wait for Link search results and choose the exact record. Leave each edited field to commit its value. Check required dates in every item row. A saved draft and a submitted record are different states. If validation fails, correct the highlighted field and verify the saved result before continuing.