Buyer A signs the awning sample the moment the bundled remote rolls the fabric out and back. Buyer B signs two weeks later, after the motor-to-channel map, the remote identities, and every open deviation are written into the approval record. Same sample, same table, same afternoon demo. Only one of them can tell the second production unit from the first without guessing.
The record is the deliverable here. Everything below is scoped to the SunSetter Essentials Motorized Awning manual, which is the only control documentation in hand and serves as a reference for what a remote-channel record should contain. It is not proof that any custom awning supplier ships the same programming, the same remote, or the same channel behavior. Approve a written configuration matrix; a working button press is not a configuration.
Freeze the Remote-Channel Matrix on Day One
On day one of a sample review, the approval sheet most buyers bring covers fabric weight, color, frame finish, and maybe dimensions on the diagonals. Add a control block before anyone touches the fabric, because the fabric conversation is easy and the control conversation is the one nobody wants to have after the container lands.
Two facts from the reference manual anchor that block. In that manual, the motorized awning is programmed at the factory to respond to channel 1 on the multi-channel remote packaged with it. Each channel on every multi-channel remote carries a unique ID, an identification code that lets one remote act as five different remotes. Both describe a default state for that model. Neither describes what your supplier will ship.
So the block needs columns, not adjectives. One row per delivered motor, one row per delivered remote, and columns for channel number, remote ID, and the physical unit each row belongs to. Leave blank fields for supplier name, model, manual revision, and written deviations, and send the blank form out with the RFQ so the supplier understands the filled version is part of the deliverable.
Blank fields do the heavy lifting. A supplier whose control system differs from the reference in remote type, channel count, or programming sequence has somewhere to say so, which turns a silent difference into a documented engineering decision. A difference with a note on the form is a decision. A difference without one is a surprise on a ladder in July.
One caution about the form: it should record the supplier's control architecture rather than force it into the reference model's vocabulary. A supplier whose remote pairs by a different scheme still owes you a written map of which control drives which motor. If their scheme cannot be expressed as numbered channels, that column stays blank and a short written description takes its place. A blank column with a paragraph beside it beats a filled column that means nothing.
Run the Pairing Rehearsal in Week One
Suppose the sample arrives with one awning, one remote, and an empty matrix. The rehearsal is not a demo; it is filling the matrix a row at a time. The cited manual's rule for multi-motor, multi-remote programming is explicit: unplug all SunSetter products and plug in only the one particular product you wish to program for the remote, at that time. Its point is that only the unit being paired should be powered. Ask the supplier in writing whether their system carries the same condition or a different one, because the answer belongs on the form either way. Only the unit under test stays powered. I would then press channel 1 and log which motor moves, press each remaining channel in turn and log the same, and record four things per press: whether a motor responded, which motor, whether two channels drive the same motor, and whether a channel is unassigned. Finally, line up the remote IDs across every unit in the shipment and flag repeats.
A remote that moves the awning fills exactly one row of that matrix. The remaining rows are the finding.
Every cell ends as a pass or a fail, and an empty cell is a fail until the supplier fills it with documentation.
Why a Moving Awning Proves Very Little
A successful press confirms the default response path and stops there. The motor answers channel 1 on the packaged remote because that is how it left the factory. The other channels, their assignments, and the identity of the unit in front of you remain untested.
Unique IDs are where two-awning jobs go wrong. Suppose a buyer receives two units for one building and never records which remote ID belongs to which awning. Unit two answers unit one's remote, the fabric moves, and nothing looks broken, because the identities were simply never written down. No component failed. The record did.
The same press also cannot show that the sample was programmed while only that unit was powered, or that the supplier's sequence is one you or your installer could repeat on site. Those are separate lines on the form, and they stay empty until someone answers them.
What the demo does prove is worth keeping: if the bundled remote cannot move the sample, nothing else on the sheet matters and the conversation ends early. Treat it as a screen, not a signature.
Deal-Breakers by the End of Week Two
Pull the approval if the supplier cannot document which channel each motor uses. Pull it if delivered remotes show duplicate or unexplained IDs. Pull it if the supplier's programming steps contradict the one-powered-device condition, because that contradiction resurfaces as a service call rather than a note. Pull it if the sample manual or model differs from the reference with no written comparison, and pull it if "it works with the bundled remote" is offered as the whole specification.
Everything outside the control block stays an open RFQ item: custom capability, MOQ, price, lead time, tooling, certification, sample test reports, and factory audit results. Put them on the same sheet as dated questions with a named owner, so the missing answers sit visibly next to the ones the matrix already covers.
Note what the matrix does not cover. Fabric, motor duty, warranty terms, and packaging are separate line items with their own evidence, and a clean channel map does not vouch for any of them.
Thirty Days Later, Audit the Channel Map
By the time the first production shipment lands a month later, the signed matrix becomes a receiving document. I would hold each incoming unit's filled map against the approved version, channel number against channel number, remote ID against remote ID, motor assignment against motor assignment, and stop the lot on a duplicate or an unassigned ID. That is the check the buyer controls, and it costs minutes per unit.
Suppose that shipment arrives with remotes that look identical to the approved sample and a map filled in from memory. That is the case the signed version exists for: the paperwork decides whether the lot moves, not the appearance. Record who checked, on what date, and which deviation was found, so the next shipment has a baseline to be measured against.
None of this proves the supplier will pass. It proves you will know at the dock instead of at the installation.
This is not for the buyer ordering a single fixed awning with no remote, and not for a team willing to accept "it works" as a specification. It is for OEM, wholesale, and QC groups that need the channel matrix, the written deviations, and the audit trail on file before anyone signs.
Comment on this brief