Features

Export Website Enquiry Attachments: Drawing Uploads, File Access and Sales Handover

Plan drawing and quotation-file uploads for an export website. Check formats, size, count, authorized access and sales handover with seven acceptance tests, inc

To receive drawings and quotation attachments on an export website, agree on the files sales needs, the customer's submission route and who may access the result. Show accepted formats, size and count limits, and an alternative contact route next to the form. Then test the saved enquiry, file access and handover so that a successful upload leads to an actionable request.

This guide is for equipment suppliers, component manufacturers, custom fabrication and engineering service websites. JLC's public enquiry instructions (Chinese) describe drawing and product-file requirements, illustrating this purchasing task. The checklist below is independently written; limits must follow the actual business and deployment. For basic fields and delivery problems, see the enquiry form guide.

1. Choose the first files around the quotation task

Ask sales and engineering to bring a sanitized example and identify which information changes the next reply. Standard products may need a model, quantity, destination market and contact details. Custom parts may require dimensions, material and quantity. Engineering services may start with operating conditions and a shareable specification. Treat establishing contact and preparing a formal quotation as separate stages, and keep a text enquiry route available for buyers still preparing drawings.

MaterialSuggested routeHandover check
Shareable specification summary or reference imageA tested website file fieldSales confirms model, revision and purpose
Proprietary drawings, customer lists or sensitive parametersA controlled transfer route accepted for the projectAgree access holders, retention and permitted onward sharing
Large files, specialist CAD or encrypted archivesCollect contact details and arrange follow-up transferEngineering and maintenance confirm format and inspection

Match collection to the service being provided. Where a buyer requires confidentiality arrangements first, the business owner confirms those arrangements before providing the appropriate route. Page promises must match the actual permissions and process.

2. Turn formats, size and count into testable rules

List business-required formats, then have developers check field settings, server validation, web server, PHP and storage limits. The usable upload range depends on the entire chain. Record the per-file limit, file count and overall request limit separately; include combined file size, request overhead and timeouts in testing.

  • Formats: list accepted extensions and prepare genuine sanitized samples. Confirm CAD types such as STEP and DWG individually, including whether engineers can read them.
  • Size and count: display both the per-file limit and maximum file count. Explain how the customer can continue when a limit is reached.
  • Revisions and identifiers: ask for project, part and revision identifiers. Agree how the project retains original names and internal identifiers.
  • Alternative route: let buyers submit text and contact details when files are unavailable or connections fail. Associate follow-up transfer with the same enquiry number.

Explain the rules in each language. On mobile, show selected names, counts and a removal control. Test which other inputs and file selections survive errors, and explicitly request reselection where required. Accept the file-picker hints together with actual server validation.

3. Separate current CatchCMS capabilities and project implementation

The current repository's public form runtime supports image/file fields, validation for single or multiple files, required fields and per-field count settings. It stores file locations in submission fields. Repository defaults set a 10240 KB per-file limit and allow PDF, Word, Excel, TXT and ZIP files; image fields have a separate image-type list. Actual production support requires checking runtime configuration, field settings and the installed theme, followed by tests with real samples.

The default uploads disk uses public access configuration. For controlled customer drawings, implement private storage, authorized downloads or temporary access links, then test anonymous access, other accounts and expiry. A form's login requirement governs submission eligibility; file-read permissions need their own acceptance checks. The download center guide covers distributing company materials to visitors. Incoming customer files need a separately agreed receiving and access policy.

CAD support, malicious-file scanning and quarantine, archive-content inspection, download auditing, retention and automatic cleanup require agreed project development and operations. Record their scope, owners and results. Enabling a format also requires the relevant content and access checks.

4. Track receipt, inspection and sales handover separately

  1. Submission: capture form, page, language, time and response, matching the success message to an actual record.
  2. Saved record: use the enquiry number to check contact details, model, file count and locations. Confirm authorized staff can retrieve the files.
  3. Inspection: record pending, usable or replacement-required outcomes, with reviewer and time. Automated transitions require project implementation.
  4. Sales handover: assign an owner, backup and next contact. Engineering confirms whether the drawings support quotation.
  5. Replacement files: relate previous files to new revisions and identify the version used for the current quotation.

CatchCMS currently saves a validated submission before sending its notification. Mail presents field values and file-location text; binary mail attachments require separate implementation. Record sending, actual inbox arrival, readable files and sales acceptance independently. If mail fails, take over from the saved record and follow the enquiry routing checklist. Access to private file links must follow the actual authorization design.

5. Assign owners for suspicious files and failed attempts

Maintenance staff should define file protection around storage and reading methods. The OWASP File Upload Cheat Sheet recommends business-specific type and size limits, content checks, and controlled storage and access. Record implementation and verification of each agreed measure during project acceptance.

Sales should refer suspicious files through the company's approved channel for inspection in a controlled environment, while preserving the text request for continued communication. For archives, agree expanded size, count and nesting checks. Encrypted files need a workable inspection arrangement. Provide a clear alternative transfer route for legitimate material.

After a timeout, search saved records by time, contact and test marker before choosing the next action. Reconcile stored files with enquiry records. Handle orphan files, expired materials and failed-upload cleanup under project rules; confirm associations, retention grounds and recovery before bulk cleanup.

6. A clearly fictional drawing-receipt example

The following example is fictional; its limits illustrate acceptance only. A component supplier plans to accept up to two PDF files of 5 MB each containing shareable sample drawings on its English quotation page. The buyer enters PX-240, quantity 50 and revision R3. In an isolated test environment, the team checks two valid files, a third file and a file above the limit, comparing messages and actual record persistence.

Sales retrieves the two files from the test record. Engineering finds that one drawing says R2, requests R3 and records which revision supports the quotation. For real proprietary designs, the team first accepts controlled storage and authorized downloads before enabling that receiving route. This example describes a workflow; actual form rules, file permissions and owners follow project delivery.

7. Complete seven acceptance checks

  1. Valid samples: submit from both language pages, including one mobile file selection. Compare fields, file counts and saved enquiry numbers.
  2. Boundaries: in testing, check per-file, file-count and overall request limits, error messages and actual persistence.
  3. Formats: check server outcomes for legitimate formats and controlled invalid samples. Technical staff perform security detection under an approved plan.
  4. Access: test authorized staff, anonymous visitors and other accounts. For private access, also test expired or revoked links.
  5. Failure handover: simulate network or notification failure, reconcile by enquiry number and record how sales resumes contact and obtains usable files.
  6. Revisions and language: supply an updated revision and check bilingual labels, referenced part identifiers and the final quotation version.
  7. Retention and handover: document owners, deadlines, cleanup scope and evidence locations, then verify the process with test data.

Use an isolated test environment, dedicated inboxes and sanitized files for boundary, failure and permission checks. Copy this register: site/language | form/enquiry number | filename/revision | type/size/count | saved result | inspection status | authorized retrieval | sales/engineering owners | missing materials | retention deadline | evidence location.

8. Common questions

Must every buyer upload a drawing?

Decide by quotation stage. Initial contact can collect the model, request and contact details. Obtain the drawings required for a custom quotation in the next stage, explaining each stage's purpose.

Is sending a file link to sales enough?

An authorized sales owner should retrieve it, and engineering should confirm readability, revision and suitability for the next action. Record notification, access, material quality and business handover separately.

What should we prepare for the implementation team?

Bring sanitized file samples, format and size ranges, public or private access requirements, sales and engineering responsibilities, and retention needs to CatchCMS project consultation. Agree backend configuration, theme integration and additional development, then validate the complete process for one product series.