RFIDBRIDGE FIELD NOTES / 01
Selection · Testing · Integration · Deployment
English
EnglishBahasa IndonesiaDeutschFrançaisEspañolItalianoPortuguêsNederlandsPolskiРусский日本語한국어Tiếng ViệtไทยTürkçeالعربية
RFIDBridge
Request a project quote

The reseller model: you hold the customer and the invoice.

The customer relationship is yours — the brand, the purchase order, the first phone call when something stops working. Our part starts behind your invoice: equipment supplied with the model and radio variant confirmed for the destination market, configuration support that reaches you before the deal closes, and an escalation path for what you do not want to carry.

PARTNERS / RESELLERONE OF THREE MODELSTerms live in a written partner agreement, not on this page.

01 / THE SHAPE OF IT

Best when
it fits this way.

Best when you hold the customer, the invoice and the first-line relationship.

This is a supply relationship with technical backing, and it is written that way honestly: it fits partners who already sell and support hardware or mobility — a barcode portfolio, a mobility fleet, a network install practice — and can absorb first-line RFID support into what their team already does. It is not a side income for a party that will forward every technical question to us; if the escalation path would carry the whole relationship, the referral model is the better fit.

Compare all three on the programme page
  • You buy and resell, and you invoice your customer.
  • We supply equipment, configuration support and the technical escalation path behind you.
  • Pre-sales support is available to you before the deal closes, not only after it is won.
  • We do not approach your registered customer directly for the same scope.

02 / WHO HOLDS WHAT

The line between
your side and ours.

YOU OWN

The relationship in front of the customer

  • The customer relationship, your quotation and your invoice — including local commercial terms, delivery scheduling and anything you promise in your own name.
  • First-line support: the calls, the resets, the "the screen says nothing" traffic, triaged by your team before it reaches us.
  • A named technical contact who can configure a handheld or point a fixed reader without us doing it for them.
  • Accuracy about the destination market. Tell us the country before we quote the variant; the certification boundary is not something either of us can resell around.
WE OWN

What we are accountable for under this model

  • Supply with the model, radio variant and certification evidence confirmed for the market actually being shipped to.
  • Pre-sales technical support — item review, tag selection, read-zone design — while the opportunity is still being won, not only after.
  • Configuration documentation you can hand your customer under your own brand.
  • A named escalation route for live deployments, and spares and availability planning before a failure forces the question.
Nothing here is an offer capable of acceptance. Margins, territory, deal registration and support obligations exist only in a written partner agreement, negotiated per partner and per market.

03 / AGAINST THE OTHER MODELS

The same decision,
three ways.

Every model page carries this table, because choosing a model means comparing it. The column you are reading is marked.

  ReferralReseller (this page)Solution partner
Customer and invoice We hold the customer for this scope; your introduction sits beside that relationship.Yours, entirely — the quotation and the invoice are your documents, not ours.Yours, including the design and the delivery decision.
Technical ownership All of it — qualification, testing, configuration, delivery and documentation.Yours, with our pre-sales support before the close and escalation behind it.You design and integrate; we validate the read, confirm the variant and supply the equipment.
Support path The customer is supported by us directly; you stay out of the escalation path.You at first line, us on the technical escalation path you define in your agreement.You on site; escalation reaches a named engineer rather than a queue.

04 / THE OBLIGATIONS

What this model
asks of each side.

These sit on top of what every partner does — a named technical contact, honest reporting, respect for the certification boundary. They are the parts that are specific to reseller.

OF YOU

  • Register the deal when there is a real opportunity behind it. Registration is what makes "we will not approach your customer" checkable rather than aspirational.
  • Tell us when a won project went badly. A reseller who reports failures accurately gets better pre-sales support on the next one; that is the whole point of the relationship.

OF US

  • No direct approach to your registered customer for the same scope. We will not use a support contact as a sales channel into your account.
  • Lead time and availability answers before you commit them to your customer, so the dates in your contract are dates we have confirmed.
  • The same variant and configuration documentation on every order of the same line, so a repeat purchase is actually repeatable.

05 / STARTING WELL

What a good first
application looks like.

  • What you sell today, who you sell it to, and what your technical team already handles for you.
  • The first projects you would bring — even at enquiry stage — rather than a general intention to add a category.
  • The markets you need variants confirmed for, so the first conversation is about real configurations and not hypothetical ones.

Applying does not create a partner relationship, and there is no qualifying threshold behind the form. The useful signal is a real situation described honestly.

Apply as a reseller partner

06 / FAQ

Questions worth
asking early.

Yes, and that is the honest condition. The model assumes your team handles first-line configuration and support with us backing it up. If you would have to forward every technical question to us, the relationship would fail at the first support call — the referral model has no such requirement.

No. Catalogue listings that carry a figure show a per-unit planning reference, not a reseller price. Commercial terms are negotiated per partner and per market, and publishing a number we would then vary is worse than publishing none.

Registration lives in the agreement, and the agreement states what survives the relationship and for how long. We would rather that answer be in writing between us than improvised at the difficult moment.

BEFORE YOU APPLY

Read the model
beside its neighbours.

Tag selection and testing What your pre-sales support actually gets from us on a new item. Support and spares The escalation tracks your customer-facing team hands into. Trade terms How a quote, a shipment and the documents that ship actually work.

RFIDBRIDGE / PARTNERS

Bring a real
opportunity.

A first conversation is more useful with a live customer situation attached than with a company profile. Both are welcome; one moves faster.

Apply now