Custom Rooftop Tent Crossbar Fit and Dimension Check Workflow

To check a custom rooftop tent's crossbar compatibility, start with the tent manual and match its mounting system to the crossbar height and width, then confirm the front-to-back bar spread before you ask for a quote. The exception is a rack from another brand or a factory-installed rack: the cited Thule guidance says to check that rack's manual to determine compatibility, and its spread figure stays inside that guide's scope rather than becoming a universal rule.

This is a document and dimension review, not a promise that any bar will fit. The buyer's job is to make the supplier answer against named documents: the tent manual for the mounting interface, the rack manual for an unknown rack, and a written dimension record for the RFQ.

On Day One, Read the Tent Manual First

Day one should begin with the tent instruction manual, not the rack product page. The cited Thule guidance for its tent and rack reference says the crossbars need a specific height and width and directs the reader to the tent manual to confirm the mounting system is compatible with those crossbars. That order matters in sourcing: the tent defines the interface, while the rack listing may describe a vehicle fit without describing the tent's mounting system.

The practical move is to copy the mounting-system name and any crossbar height and width requirement from the manual into the buyer's file. If the manual does not state a usable value, the RFQ should ask the supplier to identify the controlling document rather than accept “standard bars.” Skipping this step creates a familiar mismatch: a rack can fit the vehicle and still fail the tent's mounting interface.

Capture Crossbar Height and Width

Capturing crossbar height and width turns a vague compatibility question into a record a supplier can answer line by line. The record should include the mounting-system identifier, the crossbar height, the crossbar width, and a reference to the rack manual when the rack is not the tent maker's own. The Thule wording points to a specific height and width, not one common size that covers every tent.

Use the same field names in the buyer's sheet and the supplier's reply. A reply that gives a value without saying which document controls it has given the buyer a number to argue about later. That shared record keeps the quote comparison on the interface rather than on a general fit claim. Without that written record, two quotes cannot be compared, and a later drawing review has no baseline.

Check the Rack Manual for Other Brands

When the rack is another brand or a factory-installed rack from the car manufacturer, the tent manual may not be enough. The cited Thule guidance says to check the rack's manual to determine compatibility. That is a document request, not a note from a sales channel.

Ask for the exact rack manual or the page that covers the crossbar interface. Keep that page with the RFQ so the buyer and supplier refer to the same source. If the supplier cannot name the rack or the manual, keep the compatibility question open. If this check is skipped, the buyer may treat a tent-side requirement as a complete answer when the unresolved side is the rack. The two documents answer different questions, and the purchasing file should show both.

Verify the 28-Inch Bar Spread

Within the cited Thule guide, the front-to-back bar spread for rooftop tents must be at least 28 in/70 cm to properly support a tent. That sentence is a support requirement inside that guide's scope; it is not a claim that every brand, every tent model, or every custom design uses the same figure.

For a custom rooftop tent RFQ, compare the spread figure in the controlling manual with the spread the supplier's drawing or rack specification states. If the figure is missing, ask which document defines it. Misreading cuts both ways: treating 70 cm as an all-brand rule overgeneralizes a single guide, while treating the figure as optional inside the cited guide ignores the stated support requirement.

Build the RFQ Dimension Sheet

Build the RFQ around a one-page sheet you can actually send, not a long email that mixes fit, price, and sample requests. The sheet should list the mounting system, crossbar height, crossbar width, bar spread, the controlling manual citation for each field, and a request for the supplier's drawing reference. Improvement one: replace “universal fit” with those fields; the effect is that replies become comparable instead of yes or no. Improvement two: ask the supplier to name the document behind each dimension; the effect is that the buyer can see whether the answer rests on the tent manual or the rack manual.

A hypothetical reply of “fits all standard bars” should be marked incomplete, not approved. Keep commercial topics separate: supplier capability, MOQ, price, lead time, tooling, and certification are RFQ questions for this supplier, not assumptions the buyer can fill in from a general guide. The sheet is a control document for the interface, not a purchase order.

By Week One, Compare Drawings to the Manual

By the end of the first week, compare the supplier's drawing or specification sheet with the tent manual's requirements for the mounting system and crossbar dimensions. This is still document review, not a sample test. The goal is to see whether the supplier has restated the interface in the same terms and attached a source for each value.

If the drawing omits one of those interface fields, the sample approval discussion has no shared basis. Do not let a polished drawing replace the manual citation; a drawing can be precise about the tent and silent about the rack. The week-one check is where the buyer catches that gap while changes are still cheap.

Before Sample Approval, Freeze the Interface

Before the first sample approval, freeze the interface definition in writing: the mounting system, the crossbar height and width requirements, and the bar-spread figure as stated in the controlling manual. The cited Thule guide supports the spread statement only within its own scope, so the file should show that scope instead of turning the figure into a category rule.

This is also where the buyer separates technical approval from commercial approval. The available evidence does not establish this supplier's custom capability, MOQ, price, lead time, tooling, or certification, so those remain open RFQ items. An unwritten fit claim leaves the mismatch risk with the buyer; a frozen interface gives both sides a document to check before tooling or sample work proceeds.

One Month Later, Recheck the Compatibility File

One month after the RFQ starts, recheck the compatibility file for spec drift among the tent manual, supplier drawing, and rack manual. This is document control, not an installation test. A revised drawing, a new rack manual, or a changed mounting-system note can reopen a fit question after the buyer thought it was closed.

The recheck should compare revision dates and the controlling citation for each interface field. A short revision note in the sheet is enough; the point is to keep the citation current, not to retest the product. If one document has moved, ask for the current version and update the sheet before discussing sample approval again. If the monthly check is skipped, an old approval can outlive the document it was based on.

Today's action is to open the current tent manual and rack manual, fill the one-page RFQ sheet with the interface fields, and send it to the supplier. If any field lacks a document citation, request that document before you discuss sample approval.