Terms

01

Who this applies to

Skuply supplies businesses only. These terms apply to every quote, every connection and every month that follows. Your own purchasing conditions do not apply, unless we accept them separately and in writing.

02

What we deliver

A connection to your webshop, a pipeline running through it and a monthly report. We fill missing attributes, write the copy that follows from them, and keep it filled with every new SKU.

What we do not deliver: software you take into management, a licence, or a guarantee on revenue. Whoever buys a tool buys a screen. Here you buy filled fields.

03

What you deliver

An API key with read access to products and write access to product fields, and a contact who answers the review list within a reasonable time.

We work from what sits in your catalogue and feeds. If the source is wrong, the derived value is wrong too, and that is not a failure on our part. We do always show in the log which source it was.

04

The threshold is part of the service

Every derived value gets a number saying how direct the source is. Anything under 0.85 does not go to your shop but to the review list. That is not a setting we flip at will: higher is possible at your request, below 0.70 we will not go.

Whatever stays on the review list because nobody looks at it does not quietly go live after all. That is intended, not a fault.

05

What we never write

Price, stock, lead time, MPN and warranty are neither read nor written. A GTIN or EAN is only matched from your feed or a manufacturer database, and never generated. No match means: the field stays empty.

You can extend this list, not shorten it. If you do ask us to fill one of these fields, we refuse, and that is not a breach.

06

Draft first, live after

The first pass writes to draft. You approve a sample of two hundred products, and only then does the rest go live. Until that moment your shop is exactly as it was.

07

Rolling back

Every value sits in two places: in our own namespace with source and timestamp, and mirrored to the field your shop uses. That is why rolling back works per field and per pass, up to twelve months afterwards, as long as the contract runs. Once it ends it no longer works, because then the log is gone.

08

Price and tiers

One package, four tiers, and the meter is the number of SKUs in your sitemap. Grow past a boundary and the rate follows on the first of the next month. Drop below one and it does too.

09

Payment

Invoices are paid within fourteen days. On late payment we may suspend the service after a reminder and seven days grace. Suspending means: we write nothing further. What is already there stays there, then too.

10

Term and termination

Cancel monthly, effective the first of the next month. Paying a year in advance is allowed, with two months off; if you then cancel mid-term, we settle at the monthly rate and refund the difference.

The first pass is a one-off and is not refunded if you stop afterwards, because the work is done by then and the fields sit in your shop.

11

Thirty days money back

If it does not suit you, you get everything back within thirty days of the first go-live, including the first pass. On request we roll back everything we wrote. This applies once per customer.

12

Availability

We promise no uptime percentage, because the service is an assembly line and not a website. What we do promise: new SKUs are complete within an hour of arriving, and the monthly report comes on the first of the month.

If your shop is down or the API is unreachable, we wait and catch up. That does not count as our failure.

13

Whose data it is

The product data is yours, including the fields we derived and the copy we wrote. We hereby transfer all rights in them to you insofar as any exist. If you stop, everything stays.

The pipeline, the models, the mapping layer and everything we use to fill those fields are ours and stay ours.

14

Liability

Our liability is limited to the amount you paid in the twelve months preceding the damage. We are not liable for lost revenue, missed visibility or a ranking that disappoints.

This limitation does not apply in cases of intent or wilful recklessness, and not to fines from the supervisory authority resulting from our failure; for those the data processing agreement applies.

15

No payment on results

We charge a fixed amount and not a percentage of something. Attribution in e-commerce is a swamp, and a supplier who bills himself on revenue starts steering on revenue instead of on data.

What we put against that is measurability: at the start we record a holdout of 2,000 products we do not touch, so you can see the difference yourself.

16

Changes

If we change these terms, we say so thirty days beforehand. If you disagree, you may cancel as of that date at no cost. We change nothing silently.

17

Law and disputes

Dutch law applies to this agreement. If we cannot work it out together, the dispute goes to the court of [district]. We would rather call first.

Questions about this go to hallo@skuply.io and are answered by somebody who builds the service themselves.