Skip to main content
NNexvendo

For distributors

A reseller customer of yours asked you to send pricefiles to Nexvendo. Here's what that means.

Short version: you add one email address to your existing pricefile distribution list, exactly the same way you'd add any other reseller. No accounts, no contracts, no integration work. Below: what we are, what we ask, what we promise, and the technical + security detail your compliance team will want to verify.

What Nexvendo is

And what it isn't.

We are a procurement tool for your reseller customers.

Nexvendo aggregates pricefiles from multiple distributors into a single searchable catalog for IT resellers in Denmark, Sweden, Norway, and Finland. Resellers use us to compare distributor offers for the same SKU, build customer quotes faster, and surface refurbished inventory alongside new.

You — the distributor — already provide your reseller customers with pricefiles. We're a tool the reseller uses internally to consolidate those pricefiles. From your perspective, sending to Nexvendo is structurally identical to sending to the reseller themselves.

We are not a marketplace, distributor, or reseller.

We don't buy or sell inventory. We don't take a cut of your reseller customer's purchase from you. We don't position other distributors against you. We have no business relationship with the end customer your reseller serves.

Our business model is a subscription paid by the reseller — €49 to €599 per month depending on plan. That's our entire revenue. We have no incentive to insert ourselves between you and your reseller customer.

What we ask you to do

Two minutes of distribution-list config. That's it.

  1. 01

    Add one email address to your distribution list

    Add pricefiles@mail.nexvendo.com as a recipient on the same distribution list (or SFTP-share, or HTTPS-feed) you already use for the reseller customer who asked. Pricefiles arrive at our end, get routed to that reseller's account, and update their catalog.

  2. 02

    Subject line carries a 4-character reseller code

    Each reseller has a code like NXV-AB12. Include it anywhere in the subject line so we know which reseller the file is for. Example: "Q3 pricefile [NXV-AB12]". The reseller will tell you their code.

  3. 03

    Carry on as normal

    No further config. We accept whatever format you already send — .xlsx, .xls, .csv, .tsv, .txt. No required column order. Files can be sent from any address. Updates can be daily, weekly, monthly, or on-demand. Whatever your current cadence is.

Prefer SFTP or HTTPS? Both work. The reseller can configure either using credentials you already issue them. We pull on whatever schedule you support — we don't require you to push.

What we won't do with your data

Specific commitments, not vague reassurances.

  • We won't compete with you.

    We don't operate as a distributor. We have no inventory, no warehousing, no sales motion to your reseller's end customer.

  • We won't resell your data to anyone.

    Catalog data is purely operational. We don't share it with other distributors, with market-data brokers, or with analytics services.

  • We won't show your prices to other tenants.

    Strict Postgres Row-Level Security ensures one reseller's catalog never reaches another reseller's view. The pricefile you send for reseller A cannot be seen by reseller B even if they're a Nexvendo customer.

  • We won't use your data for ai training.

    We don't feed pricefile data into model training pipelines — neither our own nor third-party LLM providers. Catalog content stays in EU operational use only.

  • We won't re-distribute your pricefile.

    Resellers can view their copy in our portal and use it to build quotes for their customers. They cannot forward the raw file to other parties through Nexvendo.

  • We won't lock you in to anything.

    Sending to us is configuration on your distribution list — reversible at any time with no notice required. Stop sending and we stop receiving. No contracts to terminate.

Technical brief

What format we accept, what we do with the bytes.

Email delivery

  • Inbox: pricefiles@mail.nexvendo.com
  • Subject must include reseller code (4 chars after NXV-)
  • Attachment formats: .xlsx, .xls, .csv, .tsv, .txt
  • Size limit: 25 MB per attachment, multiple attachments OK
  • Encoding: UTF-8 preferred, Windows-1252 supported
  • EU decimal commas (e.g. 1.234,56) handled automatically

SFTP or HTTPS

  • You issue credentials, the reseller configures them in our portal
  • Reseller credentials are encrypted with AES-256-GCM at rest before we store them
  • We poll on a schedule the reseller picks (hourly, 4h, daily, weekly)
  • SHA-256 idempotency: we skip if the file hasn't changed
  • Read-only access — we never write to your server

Column mapping

  • No required column order or names — your existing pricefile layout works as-is
  • First time a new layout arrives, the reseller maps your columns once
  • Mapping saves automatically and applies to every future file
  • Auto-detect handles the common SKU / MPN / EAN / Stock / Price column names

Carbon data (optional)

  • If your pricefile carries an embodied-carbon column (kg COâ‚‚e per unit), we surface it on the reseller's quote PDFs
  • Nordic public-sector tenders increasingly require this — providing it makes your products more competitive in those tenders
  • Optional today; recommended for refurbished IT distribution specifically

Security brief

For your compliance team.

EU-hosted infrastructure

Production database, file storage, and application hosting all in Frankfurt, Germany. We don't replicate pricefile data outside the EEA. Hosted on Supabase (Postgres + Storage) and Vercel.

Encryption

TLS 1.2+ in transit. Distributor credentials AES-256-GCM at rest with a master key held outside the database. A read-only database dump would not reveal your credentials.

Tenant isolation

Postgres Row-Level Security policies enforce strict tenant boundaries at every table. Reseller A's catalog cannot be queried by reseller B even with valid auth.

GDPR posture

Lawful basis enumerated per processing activity. Sub-processor list published. Data Processing Addendum available at /dpa. Privacy Policy at /privacy.

For your compliance team's records: a single consolidated security overview is published at /security — print-to-PDF for one-attachment review. Live operational status at /status. Deeper FAQ at /faq.

Common questions from distributors

  • Why is the reseller asking me to send to Nexvendo instead of directly to them?

    The reseller is using Nexvendo to aggregate pricefiles across multiple distributors into one searchable catalog. Sending to us routes the file to their account in our system. They still see the file and use it; it just lands in their procurement tool instead of their inbox.

  • Do we need to sign anything?

    No. There's no contract between you and Nexvendo. The relationship continues to be between you and your reseller customer. We're just a delivery destination on the reseller's behalf.

  • Can other distributors see our pricefile through Nexvendo?

    No. Each reseller's catalog is fully isolated by Postgres Row-Level Security. A different reseller cannot see your pricefile even if they're also a Nexvendo customer. Other distributors have no access to the platform's catalog data.

  • Can the reseller forward or re-distribute our pricefile through Nexvendo?

    The reseller can view their copy in the portal and use it to build customer quotes — same as if you sent it to their inbox. They cannot mass-export and forward the raw file to other parties through Nexvendo. The portal is a viewer, not a redistribution tool.

  • What happens if we stop sending pricefiles?

    The reseller's catalog stops receiving updates and goes stale. Their portal will flag this — we surface a 'stale feed' indicator after 14 days. Nothing on our end requires any termination action; just stop sending.

  • Will Nexvendo aggregate our prices into competitive intelligence sold to other parties?

    No. Catalog data is used strictly to power the reseller's own portal. We don't sell aggregate pricing data, don't share it with market-data brokers, and don't use it as a benchmarking product. Our revenue is reseller subscriptions, not data brokerage.

  • Where is our pricefile data stored?

    Supabase Storage in Frankfurt, Germany. Each pricefile is stored at a tenant-scoped path that no other tenant can access. Database rows containing the parsed data are isolated by Row-Level Security in our Postgres database.

  • How long do you retain old pricefiles?

    Retained for the duration of the reseller's subscription so they can reference historical pricing. On reseller cancellation, retained for 30 days then deleted. Backups containing the data are purged within 35 days of cancellation.

  • Can we audit Nexvendo's security posture?

    For specific procurement reviews we can provide our DPA, sub-processor list, security overview, and answer reasonable security-questionnaire questions. Email info@nexvendo.com to start the conversation.

  • What if the reseller asks us to send to Nexvendo but we don't want to?

    Don't. Continue sending directly to the reseller as before. The reseller can manually upload the file to Nexvendo themselves — same data ends up in the same place; you're just not the path. No relationship damage either side.

Want to talk?

Procurement questionnaire, compliance review, security overview, or just a conversation about whether you and Nexvendo could partner on anything — same address either way.

info@nexvendo.com

Response within one Nordic business day.