Someone who works with businesses on hardware decisions — an IT consultant, a systems integrator, an agency that keeps running into "we also need computers" as part of a bigger project — reaches out wanting to work with Sephora as a partner. That word covers two genuinely different relationships, and treating them the same creates friction on both sides: a reseller who wants an ongoing account gets funnelled into a one-off inquiry form, or someone with a single client job gets asked to sign up for a formal partner agreement they didn't need for a one-time deal.
The direct answer: there are two real paths, and which one applies depends on whether you're building an ongoing resale relationship or bringing a specific job. Resellers — businesses that stock and resell Sephora hardware under a standing account — apply through the existing reseller flow at /marketers/apply. Deployment and referral partners — bringing a one-off or occasional client job, without carrying inventory or an ongoing account — go through the standard enterprise inquiry at /enterprise, with a field on that form to identify yourself as a partner rather than the end client. No new form, no separate process — the right one already exists for each relationship.
Why "Partner" Actually Means Two Different Things
The confusion is understandable, because both relationships genuinely involve someone other than the end customer bringing Sephora into a deal. But the shape of the relationship is different in a way that matters operationally. A reseller carries an ongoing account — inventory relationship, commission tracking, a login, a history of deals over time. A deployment or referral partner is doing something narrower: connecting a specific client's specific need to Sephora, once or occasionally, without the overhead of a standing account. Forcing either into the other's process is the actual problem this article exists to fix.
| You are | If | Go to |
|---|---|---|
| Reseller | You stock and resell Sephora hardware under an ongoing account | /marketers/apply |
| Deployment or referral partner | You're bringing a specific client job, one-off or occasional, no standing account | /enterprise (identify as a partner on the form) |
The Reseller Path
If you're building an ongoing resale relationship — carrying Sephora builds as part of your own offering, on a repeat basis — the existing reseller flow at /marketers/apply is the real path, not a workaround. It's a heavier process for a reason: it creates a login, has you review and digitally sign a partner agreement, and gives you a dashboard to track referrals, commissions, and payouts over time. That overhead is worth it for an ongoing relationship and genuinely unnecessary for a single deal — which is exactly why a separate, lighter path exists for the other case.
The Deployment and Referral Partner Path
If what you actually have is a specific client's job — a multi-seat deployment you're managing, or a client you're pointing toward Sephora directly — the enterprise inquiry at /enterprise is the right path, with one addition: a field on that form lets you identify yourself as a deployment or referral partner rather than the end organisation itself. From there, it's treated like any other enterprise inquiry — reviewed, scoped, and quoted against what the job actually needs, not against a separate partner-tier process.
This deliberately reuses the existing enterprise pipeline rather than building a new one. Our bulk procurement guide and our fleet-standardisation guide cover what a real multi-unit quote should include — the same standards apply whether the inquiry comes directly from the business that needs the machines or from a partner bringing the job on their behalf.
Why a Multi-Seat Job Gets Treated Like a Multi-Seat Job
A deployment partner bringing in a genuinely large order — the kind of multi-seat job that would get real internal attention if the end client had submitted it directly — gets exactly that attention when a partner brings it instead. The enterprise pipeline doesn't distinguish "this is big because a partner is scaling it up" from "this is big because the end client needs it" — a real order of real size gets the same internal escalation either way, based on what the job actually is, not on who submitted the form. That's not a special partner benefit; it's what the standard process already does for any large enterprise inquiry, and routing partner deals through the same pipeline means they get it automatically rather than needing a separate, parallel process to replicate it.
Referral vs. Deployment: The Same Form, a Different Role
Both roles use the same path and the same form — the distinction is about what you're actually doing on the deal, not a different process. A referral partner is pointing a client toward Sephora and stepping back; a deployment partner stays involved in specifying and managing the job itself. Neither needs the reseller account infrastructure, since neither is carrying inventory or building an ongoing resale business — they're both, in the terms this article started with, bringing a specific job rather than opening a standing account.
What Doesn't Change Either Way
Whichever path applies, the fundamentals of how Sephora prices and delivers a job don't change: landed cost plus a transparent margin, real components, and local warranty support out of the Abuja base with an experience centre in Gwarimpa. A partner-sourced deal isn't priced differently or supported differently once it's in the pipeline — the partner relationship affects how the inquiry gets attributed, not what the end client actually receives. The itemised, component-level pricing standard covered in our corporate procurement guide applies the same way whether the request came directly from the buyer or through a partner acting on their behalf — a partner-sourced quote isn't a bundled number that's harder to audit than a direct one.
Two Worked Scenarios
An IT consultant managing a 40-seat office refresh for a client in Lagos, with no intention of ever stocking Sephora hardware themselves, is a deployment partner: they submit the job through /enterprise, flag themselves as the deployment partner, and stay involved through scoping and delivery on the client's behalf. A systems integrator who occasionally points clients toward Sephora but doesn't manage the technical side of the deal is a referral partner using the same form, the same field, a lighter touch on the same process. Contrast that with a computer retailer in Port Harcourt that wants to carry Sephora builds as a standing line in their own shop, reselling on an ongoing basis — that's the reseller relationship, and it genuinely needs the account infrastructure at /marketers/apply: a signed agreement, a commission structure, and a dashboard to track deals over months, not one submission for one job.
The dividing line isn't deal size — a single deployment job can be larger than a reseller's first few resale orders. It's whether the relationship is a standing account or a one-off. A partner unsure which side of that line they're on should default to the lighter path: submitting one enterprise inquiry with the partner field costs nothing and commits to nothing, while the reseller application is worth the setup only once there's real, repeat volume behind it. For a sense of what "real volume" costs a business over a multi-year refresh cycle — relevant if a reseller relationship is what's actually being considered — our fleet TCO breakdown covers the numbers behind a standing hardware relationship, not just a single order.
Nigeria Context: One Process, Not a Parallel Bureaucracy
A common failure mode for partner programmes generally is building a separate process that's slower and more opaque than just dealing with the company directly — which defeats the point of partnering at all. Routing deployment and referral partners through the same enterprise pipeline every direct customer uses avoids that specifically: the same response timeline, the same scoping process, the same escalation for a genuinely large job. The only thing that's different is knowing, internally, that a partner brought the deal — which matters for attribution, not for how the client gets served.
What We'd Actually Recommend
Figure out which relationship you actually have before you apply anywhere. If you're building an ongoing resale business, the account-based reseller flow is worth the setup overhead. If you're bringing one client's job — deployment or referral, doesn't matter which — the standard enterprise inquiry with the partner field is the faster, correct path, not a workaround for not having a formal account. Sephora Systems, a custom PC and workstation builder based in Abuja with an experience centre in Gwarimpa, built both paths to match how the relationship actually works, not to funnel everyone through the heavier one by default.
When in doubt, the cost of guessing wrong is low either way: a reseller application that turns out to be premature just sits unused until the volume shows up, and an enterprise inquiry that turns out to be the start of an ongoing relationship can always graduate to a formal reseller account once that pattern is clear. Neither path locks a partner out of the other later.
Building an ongoing resale relationship? Apply as a reseller partner. Bringing a specific client's deployment or referral instead? Submit it through the enterprise inquiry and identify yourself as a partner on the form.