What Files Should You Send to a Suspension Manufacturer for Custom Development?

For custom suspension development, send a controlled project package rather than a collection of unrelated photos and email messages. These custom suspension development files help the manufacturer understand vehicle fitment, suspension requirements, engineering targets, and the expected approval process before prototype work begins. The most useful package normally includes 2D drawings, relevant 3D CAD, vehicle and suspension measurements, reference-shock information, vehicle/load data, photos, performance requirements, test and approval criteria, product-identification requirements, and commercial information such as sample and production quantities.

BEDO’s drawing-based suspension development service describes custom development from customer drawings, CAD files, existing samples, and vehicle requirements. The important point for buyers is that no single file usually describes the complete project. A CAD model may define geometry but not rider load; a physical shock may show dimensions but not the performance target; a vehicle name may identify the platform but not the modified suspension.

A better rule is:

Geometry Files + Measurement Data + Vehicle Loads + Existing Product Reference + Performance Target + Approval Requirements = A Usable Development Package

Start with a One-Page Project Brief

Before opening the CAD folder, create one project-summary file that tells the manufacturer what the project actually is. This can be a PDF, spreadsheet, or controlled RFQ cover sheet. The format matters less than clarity and revision control.

Include:

• project name or code;
• target ATV or off-road vehicle;
• model year and variant where relevant;
• front or rear suspension position;
• replacement, performance, heavy-duty, long-travel, or other project type;
• current suspension problem;
• intended improvement;
• target market;
• prototype quantity;
• expected production quantity;
• buyer engineering contact;
• purchasing contact;
• current project revision.

This first file gives context to everything else. Without it, an engineer may receive shock_final.dwg, several photographs, and an old spreadsheet without knowing which one represents the current requirement.

Send 2D Drawings for Controlled Dimensions and Interfaces

A dimensioned 2D drawing is one of the most useful files for a suspension manufacturer because it defines the dimensions that purchasing and engineering expect to control.

For a shock absorber project, the drawing may include:

BEDO’s shock measurement guide emphasizes extended and compressed dimensions, stroke, mounting holes, mounting widths, and other installation data as separate inputs.

Do not rely only on a screenshot of a CAD drawing. Supply the controlled drawing file and a readable PDF version when possible so both engineering and purchasing can refer to the same revision.

Send 3D CAD When Geometry and Packaging Matter

3D CAD becomes more important when the project involves limited installation space, reservoir packaging, longer travel, modified control arms, new shock-mount positions, or possible interference with tires, frame members, steering, hoses, or other components.

For a normal replacement shock, full vehicle CAD may be unnecessary.For a long-travel or highly customized project, the supplier may need relevant portions of:

• chassis shock mounts;
• control arms;
• knuckle/upright;
• wheel and tire envelope;
• steering components;
• axle or driveline geometry where relevant;
• bodywork around the shock;
• bump-stop location;
• spring envelope;
• reservoir mounting area.

BEDO’s custom suspension development from drawings supports CAD-based engineering review. If the complete vehicle model contains proprietary information, send only the assemblies and hard points required for suspension evaluation.

Common exchange formats may include STEP, IGES, Parasolid, DWG, or DXF depending on the software being used, but confirm the exact accepted format with the manufacturer before transfer rather than assuming every engineering team uses the same CAD environment.

Do Not Send CAD Without a Drawing Revision

A 3D file named ATV_NEW_FINAL_STEP.stp does not tell the manufacturer whether it is newer than ATV_NEW_FINAL2.stp.

Use controlled file names such as:

ProjectCode_RearShock_Assy_RevB.step

and link that CAD revision to the project brief and 2D drawing.

Your package should make it possible to answer:

Which exact geometry was used to manufacture this prototype?

If that answer cannot be reconstructed later, sample approval becomes difficult to control.

Send a Measurement Sheet When You Are Starting from an Existing Vehicle

Not every buyer has complete engineering drawings. Aftermarket brands, distributors, and specialty vehicle builders often start with an existing ATV and a physical shock.

In that case, create a measurement sheet covering the original component and vehicle interface. BEDO’s ATV shock measurement guide is especially relevant to this development route.

Record:

• extended length;
• compressed length where it can be measured correctly;
• usable stroke;
• upper mounting-hole diameter;
• lower mounting-hole diameter;
• upper mounting width;
• lower mounting width;
• sleeves and bushings;
• shock-body diameter;
• spring outer diameter;
• spring free length;
• current preload position;
• reservoir dimensions where applicable;
• hose length where applicable;
• installation angle or photographs showing orientation.

Label every measurement reference clearly.“Length = 420 mm” is not enough if the supplier cannot tell where the measurement begins and ends.

Send High-Quality Photos, but Do Not Use Photos as Dimensional Proof

Photographs are useful because they show information that a table may miss. Send clear images of:

• the complete ATV;
• front and rear suspension;
• installed shock;
• upper mounting point;
• lower mounting point;
• surrounding clearance;
• tire-to-suspension relationship;
• reservoir and hose routing;
• original shock removed from the vehicle;
• any interference or damage;
• current spring and adjuster settings.

Add a ruler or labeled reference only where useful, but do not treat perspective photographs as accurate dimensional evidence.

Photographs answer “what does the installation look like?” Drawings and measurement sheets answer “what dimensions must be manufactured?” Both are useful for different reasons.

If You Have an Existing Shock Sample, Create a Sample Record

A physical reference shock can significantly improve development efficiency, but only if its condition is documented.

Before shipping the sample, photograph it and assign a sample ID.Record:

• source vehicle;
• model/year/variant;
• front or rear position;
• mileage or usage if known;
• whether it is original or aftermarket;
• known modifications;
• leakage;
• worn bushings;
• damaged threads;
• bent mounting eyes;
• corrosion;
• spring condition;
• missing spacers or sleeves;
• whether the sample still performs correctly.

BEDO’s sample-based shock absorber customization can use a physical reference as a development starting point, but a used part should not silently become the design standard.

The supplier must know whether a feature is intentional or simply the result of wear.

Send Vehicle and Load Data in a Structured Spreadsheet

Mechanical geometry alone cannot define the correct spring and damping specification. If the manufacturer is expected to help develop suspension performance, supply actual operating-load information.

A practical spreadsheet can include:

If several vehicle configurations exist, place them on separate rows instead of combining them into one “average load.”

This is particularly important for spring development because a rear utility ATV carrying equipment can require a different engineering assessment from the same vehicle used unloaded for recreational riding.

Send Suspension Geometry Data for Long-Travel Projects

If the target is greater wheel travel, files should define the suspension system rather than only the shock.

BEDO’s development approach for custom off-road suspension highlights the relationship between geometry, shock movement, and vehicle requirements.For a long-travel project, relevant files may need to show:

• upper shock hard point;
• lower shock hard point;
• control-arm pivots;
• wheel center;
• wheel path;
• ride height;
• full droop;
• full bump;
• target wheel travel;
• shock angle;
• existing shock stroke;
• proposed shock stroke;
• tire envelope;
• joint and axle movement;
• bump-stop position.

Do not enter “200 mm wheel travel” into a shock-stroke specification without geometry analysis. Shock movement and wheel movement are not automatically equal.

Send Spring Data Separately from Shock Dimensions

If the project uses an existing approved spring, include its controlled specification.

Possible data includes:

• spring rate with complete units;
• free length;
• inner diameter;
• outer diameter;
• wire diameter where relevant;
• coil count;
• installed preload;
• load–deflection curve if available;
• working range;
• surface finish;
• spring drawing or supplier part number.

If the spring still needs development, do not invent a rate simply to complete the RFQ. Mark it as:

Supplier Engineering Proposal Required

and provide vehicle/load/sag data instead.

BEDO’s suspension sample development covers spring development as part of the engineering process, so the development package should distinguish approved values from values the supplier is expected to recommend.

Send Existing Damping Data if You Have It

If the current shock has been tested, include the relevant test file instead of summarizing it as “too soft” or “3000 N damping.”

Useful files can include:

• force–velocity graph;
• test report;
• test speed conditions;
• compression curve;
• rebound curve;
• adjustment position;
• fluid temperature where relevant;
• shock configuration;
• spring configuration if it affected the test setup;
• test equipment or method reference where available.

If you do not have damping data, provide the observed behavior instead:

Excessive rebound after large bumps.
Bottoming with defined cargo.
Harshness over small repeated rocks.
Damping changes during prolonged rough use.

The manufacturer can then determine which engineering data must be developed rather than trying to interpret an unsupported damping number.

Create a “Current Problem vs Target Result” Document

One of the highest-value files is often not CAD at all. It is a simple engineering problem statement.

For example:

This file prevents engineers from optimizing the wrong characteristic.

“Make the shock stronger” is not an engineering target.

Send Terrain and Duty-Cycle Information

Include photographs, short descriptions, or video references showing where the ATV will operate.

State:

• farm/utility use;
• gravel;
• trail;
• rocky terrain;
• mud;
• sand;
• repeated corrugations;
• commercial fleet use;
• intermittent vs continuous operation;
• approximate operating duration;
• typical operating speed;
• cargo status during rough use.

This information helps distinguish a normal replacement project from heavy-duty, performance, adjustable, or reservoir-shock development.

Send Test Requirements Before the Prototype Is Built

Do not wait until the sample arrives to decide what “approved” means.

Create an acceptance-requirements document covering the tests your project actually needs.

Possible areas include:

BEDO’s prototype shock absorber development guidance treats prototype validation as part of development rather than simply asking whether the sample “looks OK.”

Separate Buyer Requirements from Supplier Proposals

Your documentation should use clear status labels.

A useful four-level system is:

Fixed Requirement
Must be achieved.

Reference Data
Describes the current product or vehicle but can potentially change.

Supplier Proposal Required
Manufacturer should recommend a solution.

Pending Validation
Final value depends on prototype testing.

This distinction can prevent an original shock’s existing spring rate from accidentally becoming a mandatory specification when the entire purpose of the project is to improve load support.

Send Branding Files Only After Technical Versions Are Clearly Identified

For OEM/private-label projects, branding files may include:

• logo artwork;
• label layout;
• color requirements;
• packaging artwork;
• carton labels;
• barcode information;
• buyer SKU;
• instructions;
• application label.

Vector artwork such as AI, EPS, SVG, or print-ready PDF may be useful depending on the supplier’s workflow, but confirm accepted file formats before production.

More importantly, keep branding connected to a controlled technical version.

If Shock A and Shock B use different springs or damping specifications, they should not receive indistinguishable labels simply because they use the same private-label brand.

BEDO’s custom-development and OEM approach makes it useful to maintain technical approval separately from visual branding approval.

Do Not Send Sensitive CAD Without Defining File-Control Rules

Custom suspension projects may contain proprietary chassis hard points, vehicle geometry, private-label artwork, or unreleased product information.

Before sending sensitive files, clarify:

• confidentiality arrangements;
• which employees or engineering teams need access;
• whether suppliers or subcontractors receive the files;
• permitted use;
• whether files may be retained after the project;
• design ownership;
• ownership of newly developed drawings;
• exclusivity requirements if any.

Do not assume that the words “OEM” or “ODM” automatically define ownership or confidentiality.

If only six suspension hard points are needed, sharing an entire unreleased vehicle assembly may create unnecessary IP exposure.

Use a Structured Folder Instead of an Email Attachment Chain

A practical project folder can look like this:

ATV-Suspension-Project/
│
├── 01_Project-Brief/
│   └── Project_Brief_RevA.pdf
│
├── 02_Vehicle-Data/
│   ├── Vehicle_Load_Data.xlsx
│   └── Vehicle_Photos.pdf
│
├── 03_Drawings/
│   ├── Rear_Shock_RevB.pdf
│   └── Rear_Shock_RevB.dwg
│
├── 04_CAD/
│   └── Rear_Suspension_Interfaces_RevB.step
│
├── 05_Reference-Sample/
│   └── Sample_001_Record.pdf
│
├── 06_Spring-Damping/
│   ├── Spring_Requirements.xlsx
│   └── Damping_Test_Current.pdf
│
├── 07_Test-Requirements/
│   └── Prototype_Acceptance_RevA.pdf
│
├── 08_Branding-Packaging/
│   └── Packaging_Artwork_RevA.pdf
│
└── 09_RFQ/
    └── RFQ_RevA.pdf

This is a recommended buyer-side organization, not a BEDO-mandated folder structure. Its value is revision clarity.

Create a File Register Before Sending the Package

Add a simple index showing which documents are current.

When a supplier returns questions, both sides can reference the same document names rather than saying “the drawing from last Tuesday.”

What Files Are Required for Different Custom Development Routes?

Not every project needs every file.

The strongest package is the smallest set of files that accurately defines the engineering problem, not the largest folder you can upload.

How Does a Manufacturer Turn These Files into a Prototype?

A controlled development sequence should look broadly like:

Requirement Review → Data Check → Engineering Questions → Drawing/Specification Proposal → Prototype → Vehicle/Test Validation → Revision → Approved Sample → Pilot Production → Production Release

BEDO describes development from drawings, CAD files, samples, and vehicle requirements through its custom suspension development process, while its sample development process covers engineering review, prototype work, adjustment, and validation.

The most important handoff occurs when the approved prototype becomes a repeatable production specification. Make sure the final product code points back to the correct drawing, spring, damping version, hardware, finish, and packaging.

How Should You Ask BEDO for Custom Suspension Development?

Ningbo Bedo Auto Parts Co., Ltd. manufactures shock absorbers and suspension springs and supports custom off-road suspension projects. You can review BEDO’s company capabilities before preparing the development package.

A useful first submission should contain:

Project brief + vehicle/application information + drawing or sample + main dimensions + loads + current problem + target result + sample quantity + forecast volume.

Then add CAD, detailed spring/damping data, test criteria, packaging, and other documents according to project complexity.

This gives BEDO enough context to determine whether an existing platform can be adapted or whether deeper custom development is required.

Frequently Asked Questions

1. Do I need CAD files to start custom suspension development?

Not always. BEDO also supports development from drawings, existing samples, measurements, and vehicle requirements. CAD becomes particularly valuable when suspension geometry, packaging, long travel, reservoirs, or interference are important.

2. Is a PDF drawing enough?

It can be enough for preliminary review if it contains clear dimensions and interfaces. For geometry-sensitive projects, editable 2D or 3D engineering files may also be useful. Confirm the manufacturer’s accepted formats before transfer.

3. Can I send only an original shock sample?

You can use a sample as a starting point, but also send the vehicle application, load information, current problem, and target improvement. A physical component alone does not explain why it is being redesigned.

4.Should photographs be included when I already have CAD?

Yes, where useful. Photos show real installation, surrounding components, routing, damage, and vehicle modifications that may not be obvious in a simplified CAD model.

5. Do I need to provide the spring rate?

Only if it is already an approved requirement. If spring development is part of the project, provide load, geometry, sag, and performance information and ask the manufacturer to evaluate the spring specification.

6. What damping files should I send?

If available, send force–velocity curves, test conditions, adjuster positions, and the tested shock configuration. If no damping data exists, describe the real vehicle behavior you want to improve.

7. Should packaging artwork be sent with the first engineering inquiry?

It is usually more important to establish technical feasibility first. Branding and packaging can be prepared in parallel, but final artwork should remain linked to the approved technical configuration.

8.What should I send for a long-travel suspension project?

Send the relevant suspension CAD or hard points, control-arm geometry, shock mounts, wheel/tire envelope, target wheel movement, existing shock dimensions, loads, and movement constraints.

9. How should I protect proprietary CAD files?

Share only the data required for the project and clarify confidentiality, access, permitted use, ownership, and retention before transferring sensitive files.

10. What is the minimum package I should send BEDO?

For initial review, prepare the vehicle/application, suspension position, reference shock or drawing, key measurements, rider/load conditions, terrain, current problem, target result, sample quantity, and forecast volume. From there, BEDO can identify which additional custom suspension development files are required.

Conclusion

The best custom suspension development files do more than show what the component looks like—they define what the suspension must fit, support, control, and achieve. Start with a project brief, then add controlled 2D drawings, relevant CAD, measurements, reference-sample records, vehicle/load data, spring and damping information, photos, terrain and duty-cycle details, prototype acceptance criteria, and commercial requirements. Keep every important file under revision control and clearly separate fixed buyer requirements from reference values, supplier proposals, and items still awaiting validation. BEDO supports custom suspension development from drawings, CAD files, existing samples, and vehicle requirements, together with prototype and small-batch project support. To begin a project, contact BEDO with the available files and project summary so the engineering team can identify what is sufficient for review and what additional data should be prepared before prototype development.