An export website can use a dedicated sample-request path to collect the model, quantity, evaluation purpose and destination region. Sales then confirms availability, costs, delivery arrangements and the next contact date. The initial acknowledgement confirms receipt of the request; shipment follows the arrangement agreed with the customer. This gives sales a usable handover and helps technical staff understand the planned test.
This guide is for component, equipment-part and material suppliers running a product and enquiry website. It provides fields, a manual workflow and acceptance checks. See the multi-product quotation guide for purchasing lists and the distributor application guide for channel qualification. This article focuses on evaluation samples, confirmation and feedback.
1. Define the task behind a sample request
A product page's sample link should explain eligible products, evaluation purposes, destination coverage and the confirmation process. Keep a clear model path for buyers who know the item. Offer selection assistance and a purpose field for those who need help. For custom prototypes, have technical staff review drawings, process requirements or test goals before agreeing the scope.
General quotations, sample evaluation and support for purchased products can have separate options, with a common contact route for visitors who need guidance. Preserve the source product, page language and customer's original explanation. Sales confirms the delivery plan after reviewing the request.
Publish the actual policy: eligible products, how quantities are confirmed, how sample and freight charges are checked, and the reply channel. Claims about free samples, stock or dispatch times need business evidence. Assign an owner to keep these conditions current.
2. Collect enough information for one evaluation decision
| Group | Suggested information | Handover check |
|---|---|---|
| Product | Model or product link, specification, quantity and unit | Match model and specification; mark selection assistance separately |
| Purpose | Application, performance to evaluate and key operating conditions | Technical staff can assess the test goal and applicability |
| Stage | Evaluation stage, desired receipt date and optional expected purchasing volume | Keep the requested date and confirmed date in separate fields |
| Destination | Country or region and city where needed | Sales checks service coverage and later shipping requirements |
| Contact | Company, contact and business email or usable reply channel | Identify who will confirm the request and receive the reply |
| Extra | Optional notes and relevant document links | Agree drawing uploads and sensitive material handling separately |
One approach is to collect the destination region first, then obtain the recipient, address, postal code and logistics contact through the agreed channel after confirming sample availability. Businesses needing the complete address initially should explain its purpose and handling and provide a privacy route beside the form. Choose fields to fit the actual delivery process and limit unrelated information.
Give a helpful entry example such as “PX-240-A, 2 pieces, for assembly-clearance testing.” Verify quantity rules, model availability and submission protection on the server. Recheck models supplied through URL parameters. See the enquiry attachment guide for file scope, access and handover.
3. Record receipt, confirmation, shipping and feedback separately
- Receive: Save a request ID, submission time, original fields and language. Explain that the team will confirm the next step. Test record storage and notification as separate outcomes.
- Review: Sales obtains missing details and technical staff checks the model and test purpose. Record the reason and next action for outcomes such as awaiting details, available or alternative required.
- Agree: Confirm the model, quantity, sample charge, freight responsibility, destination and expected arrangements with the customer. Recheck the receiving address and retain changes by version.
- Ship: After the responsible team confirms the arrangement, record the actual dispatch time, carrier information and related documents. Update the customer through the actual logistics process.
- Follow up: Agree the test goal, planned feedback date, sales owner and backup. Record the result and next selection or quotation action.
At modest volume, a controlled register and business email can run these steps. Each request needs a current status, owner, next action, planned date and evidence of the latest communication. Use the quotation workflow for quotation revisions and validity, and the routing checklist for regional sales handover.
Payments, orders, inventory reservations, logistics interfaces, subscriptions and communities each require a defined project scope, system ownership, permissions and acceptance criteria. Paid samples need an agreed payment and order process. Page copy and acknowledgements should match the steps the team can execute.
4. Share facts across languages and review each version
Keep models, units, request IDs, status codes and policy versions consistent. Review Chinese and English labels, help text and acknowledgements separately. Preserve the customer's original text and have sales or technical staff confirm translations. Name desired receipt dates, confirmed dispatch dates and expected purchasing volumes separately in both languages.
Check product context when entering from a product page and verify models and policy prompts after switching languages. Preserving entries across languages, saved drafts and resumable attachments require project design and tests. Where a switch affects entered data, explain how customers should handle their current input first. See the multilingual maintenance checklist.
Provide eligible products, conditions, required information and next steps in readable page text for search and retrieval tools. Titles and descriptions should reflect the actual request task. Use structured data matching the page purpose and verified information. Measure indexing, visits, qualified requests and feedback through actual observations.
5. Rehearse one fictional request
This is a fully fictional business exercise. Customer A requests two PX-240-A units for assembly evaluation, hopes to receive them in the first week of next month and lists Germany as the project destination. Sales records SR-001. The technical owner confirms suitability for the stated test and asks for interface dimensions.
After receiving the dimensions, the team confirms quantity, charges and freight arrangements and checks receiving details through the agreed channel. Sales records the customer's desired date separately from the confirmed dispatch plan. After dispatch, the team records logistics evidence and agrees a feedback date following receipt. A proposed change from model A to B requires the reason, technical suitability and customer confirmation before updating the record.
Acceptance should connect SR-001's original request, additional details, agreed revision, shipping evidence, owner and feedback plan. All identifiers, quantities and destinations in this example illustrate the workflow. Use the project's confirmed policies and data in production.
6. Define the CatchCMS configuration and development scope
CatchCMS provides content models and dynamic fields, multilingual content maintenance and forms and submission-record foundations. A customer project can configure product fields and design sample-request links in its theme. The official site's current model serves articles and feature explanations. A production sample process needs configuration and acceptance on its target site.
Automatic product context, multi-line requests, model-dependent validation, status workflows, automatic routing, customer progress views, inventory and logistics connections, CRM synchronization, payments and orders each require project development requirements and acceptance. Start with a manual register through request and feedback, then choose automation based on volume and maintenance cost.
7. Check seven outcomes before launch
- Enter from a known model and from a selection-assistance scenario. Check the links, fields and acknowledgement.
- Test valid quantities, invalid models, missing required fields and destinations awaiting confirmation. Inspect server handling and understandable messages.
- Use dedicated test data to check stored records, email and staff handover. Provide a traceable handling route for failed notifications.
- Compare models, units, policy versions and date meanings in both languages. Test how switching handles entered data.
- Rehearse additional details, substitute models, cancellation and receiving-address changes. Check confirmation evidence and current status.
- Read the explanation and complete a test form on mobile. Check labels, buttons, long models, titles, descriptions, canonical and language links.
- Have the owner and backup take over a record and locate customer confirmation, delivery arrangements and the next feedback date.
Should every sample be free?
Explain sample charges, freight and confirmation conditions according to the company's verified policy. Sales confirms each item before shipping.
When should the address be collected?
Choose initial collection or the delivery-confirmation stage to fit the business process, explain the purpose and have the customer and handler verify receiving details.
What materials start a project?
Bring one product family, a sanitized sample request, actual charging and regional rules, language requirements and an owner to CatchCMS project consultation to confirm forms, themes and development scope.