Logo Fluxy.One
About
Features
{SMB Solution}
Industries
  • Textile
  • Electronics
  • Furniture & Mattresses
  • Steel & Iron
  • Toys
  • Building Materials
  • CE Marking / GPSR
Blog
Contact
English
English
Español
German
French
Saas Webflow Template - Charlotte - Designed by Azwedo.com and Wedoflow.com

API Partnership Terms

FLXY.io | Fluxy.One API Partnership Agreement
Version 2.0 — February 13, 2026

SIA Fluxy One
Reg. No. LV40203559086
Rupniecības iela 16-14B, Riga, LV-1010, Latvia
Email: legal@fluxy.one
API Support: api@flxy.io

Note: This document is the official English version. In the event of any discrepancies between this version and translations into other languages, the English version shall prevail.

1. GENERAL PROVISIONS

1.1 Parties and Subject Matter

This API Partnership Agreement ("Agreement") is entered into by and between:

(a) SIA Fluxy One (Reg. No. LV40203559086, Latvia), hereinafter referred to as "Fluxy," "We," "Us," or "Provider," and

**(b) The legal entity accepting these terms, hereinafter referred to as "Partner," "You," or "API Partner."

Subject Matter:

Fluxy grants the Partner access to the FLXY.io API ("API") to integrate Digital Product Passport (DPP) creation capabilities into the Partner's products, services, or platforms via an embedded Zero Box form.

IMPORTANT: Partnership Model

This is a referral partnership, not a white-label or subprocessor relationship:

  • Partner embeds Fluxy's Zero Box creation form in their platform
  • End-Users create DPPs and receive direct access to Fluxy's Zero Box dashboard
  • End-Users have a direct contractual relationship with Fluxy (governed by Zero Box ToS)
  • Partner earns revenue share when End-Users upgrade to paid tiers

1.2 Definitions

"API" means the FLXY.io Application Programming Interface, including all endpoints, webhooks, embed forms, and related documentation.

"API Partner" means an entity authorized to integrate the FLXY.io embedded form or API into their own products or services.

"End-User" means a customer of the API Partner who creates a DPP through the Partner's integration. End-Users are Fluxy's direct customers (not Partner's customers for DPP purposes).

"Embedded Form" means the Fluxy-provided iframe or JavaScript widget that Partner integrates into their platform for instant DPP creation.

"DPP" means Digital Product Passport, as defined in Zero Box ToS.

"GS1 Digital Link" means a web-based product identifier compliant with GS1 standards (e.g., https://dpp.flxy.io/01/{GTIN}).

"Revenue Share" means the commercial arrangement whereby Partner receives a percentage of recurring revenue from End-Users who upgrade to paid Zero Box tiers. Specific percentages are confidential and defined in a separate Commercial Appendix.

1.3 Relationship to Other Agreements

This Agreement governs API/Partnership access only. It does NOT replace:

  • Zero Box Terms of Service (governs End-User relationship with Fluxy)
  • Privacy Policy (applies to all personal data processing)
  • Commercial Appendix (confidential revenue share terms, signed separately)

CRITICAL: End-Users are subject to Fluxy's Terms, not Partner's Terms (for DPP services).

1.4 Conclusion and Acceptance

This Agreement is deemed concluded when:

  • Partner completes the API Partner application at https://fluxy.one/api-partnership
  • Partner receives API credentials and embed code via email
  • Partner integrates the embed form or makes the first API call

By using the API, you confirm:

  • You have authority to bind your organization to this Agreement
  • You have read and agree to our Privacy Policy
  • You understand the referral model (End-Users are Fluxy's customers, not yours)

2. HOW THE INTEGRATION WORKS

2.1 Embedded Form Integration (Primary Model)

Workflow:

Step 1: Partner Integration

  • Partner embeds Fluxy's Zero Box creation form into their platform
  • Integration options:
    • iframe: Simple embed (HTML)
    • JavaScript widget: Customizable styling
    • API endpoint: Full control (for advanced partners)
  • Example use case: Avery's label design platform includes "Add GS1 QR Code" button

Step 2: Instant DPP Creation

  • End-User clicks button in Partner's platform
  • Fluxy form appears (in partner's interface, but Fluxy-branded or co-branded)
  • End-User fills in:
    • GTIN (validated against GS1 standards)
    • Product name, brand, basic description
    • Language (any language — AI will translate)
  • Fluxy instantly:
    • Creates Zero Box DPP
    • Translates to English Master Data (JSON)
    • Generates GS1 Digital Link QR code (PNG/SVG)
    • Returns QR code to Partner's platform

Step 3: Partner's Workflow

  • Partner receives QR code image (API response or download link)
  • Partner uses QR code in their product (e.g., prints on label, sticker, packaging)
  • Partner handles their own business flow (design, printing, payment to Partner, shipping)
  • NO ongoing technical work required from Partner after initial integration

Step 4: End-User Receives Email from Fluxy

  • End-User automatically receives email from noreply@fluxy.one with:
    • Subject: "Your Product QR Code is Ready – Access Your Zero Box Dashboard"
    • Link to Zero Box dashboard (https://zero.flxy.io)
    • Login credentials (or account creation link)
    • Option to edit/enhance DPP data
    • Option to upgrade to paid tiers (DPP Light €9.99, Extended €29.90, Pro €49.90)

Step 5: Revenue Share

  • If End-User upgrades to a paid tier, Partner earns revenue share
  • Revenue share percentage is confidential (defined in Commercial Appendix)
  • Payouts sent monthly within 15 days of month-end

2.2 Technical Requirements

Partner must provide:

  • Valid HTTPS domain (for iframe/widget embedding)
  • Basic integration testing (sandbox environment provided by Fluxy)
  • Disclosure to End-Users that "DPP powered by Fluxy.One" (see Section 4.3)

Fluxy provides:

  • Embed code (iframe/JavaScript)
  • API documentation at https://docs.flxy.io
  • Sandbox environment for testing
  • Real-time revenue dashboard at https://partners.flxy.io
  • Technical support during integration

2.3 Customization and Co-Branding

Standard Integration (Default):

  • Embed form shows Fluxy branding ("Powered by Fluxy.One")
  • End-User email sent from Fluxy (with Fluxy logo)

Co-Branded Integration (Optional, Requires Approval):

  • Partner logo displayed alongside Fluxy logo
  • End-User email includes Partner mention ("Your [Partner Name] product QR code, powered by Fluxy.One")
  • Requires written approval from Fluxy (email partnerships@fluxy.one)

White-Label Integration (Enterprise Only):

  • Available only for strategic enterprise partners with custom contracts
  • End-User never sees Fluxy branding
  • Requires separate pricing (flat fee, not revenue share)
  • Contact partnerships@fluxy.one for quote

3. RATE LIMITS AND CAPACITY

3.1 No Hard Limits for Enterprise-Scale Partners

For Partners operating on revenue share model: There are NO strict rate limits on DPP creation volume. We support enterprise-scale operations.

Fair Use Capacity Guidelines:

Partner Tier Expected Volume Sustained Rate Burst Capacity
Standard (most partners)Up to 10,000 DPPs/day500 DPPs/minute1,000 DPPs/minute (10 min)
Enterprise (Avery-scale)Unlimited5,000 DPPs/minute10,000 DPPs/minute (10 min)

Example: Avery Scale
Annual volume: 1 billion stickers/year
Daily average: ~2.7 million DPPs/day
Peak rate: ~5,000 DPPs/minute sustained
Supported: ✅ Yes, with Enterprise tier (no additional cost for revenue share partners)

3.2 Fair Use Policy

What is acceptable:

  • Normal business operations (printing labels, packaging, product launches)
  • Seasonal peaks (holiday sales, marketing campaigns)
  • Reasonable testing (up to 1,000 test DPPs in sandbox)

What constitutes abuse:

  • Mass DPP creation without legitimate business purpose (test spam, benchmarking competitors)
  • Reselling API access to third parties (violation of Section 2.4)
  • DDoS or malicious traffic patterns
  • Creating DPPs for products you don't actually sell/manufacture

Response to abuse:

  • First incident: Email warning and request to cease activity
  • Second incident: Temporary API suspension (24-48 hours)
  • Repeated violations: Account termination without refund

3.3 Capacity Planning

If you anticipate:

  • More than 10,000 DPPs/day (Standard → Enterprise tier)
  • More than 100,000 DPPs/day (contact us for infrastructure planning)
  • More than 1 million DPPs/day (Avery-scale — requires 30-day advance notice)

Contact api@flxy.io to: Ensure infrastructure capacity, Discuss Enterprise tier (if needed), Receive dedicated technical support, Plan integration timeline.

4. DATA PROCESSING AND PRIVACY

4.1 Critical: End-Users Are Fluxy's Customers

IMPORTANT DISTINCTION:
When an End-User creates a DPP through Partner's integration, the data processing relationship is:
  • End-User ↔ Fluxy (DIRECT):
    • End-User receives email directly from Fluxy
    • End-User creates account on https://zero.flxy.io
    • End-User agrees to Fluxy's Zero Box Terms of Service and Privacy Policy
    • Fluxy is the Data Controller for End-User's account data and DPP content
    • End-User can exercise GDPR rights directly with Fluxy (dpo@fluxy.one)
  • Partner ↔ Fluxy (REFERRAL):
    • Partner provides minimal data to Fluxy via API (GTIN, product name, basic info)
    • Partner does NOT access End-User's Fluxy account or dashboard
    • Partner receives only QR code image (PNG/SVG) — public data, no personal information
    • Partner is NOT a Data Processor for Fluxy's End-User relationships
    • Partner is NOT a Data Controller for DPP data (unless Partner also collects End-User data for their own purposes)
  • Partner ↔ End-User (SEPARATE):
    • Partner has their own business relationship with End-User (e.g., Avery sells labels to customer)
    • Partner's own privacy policy governs their relationship (billing, shipping, etc.)
    • This is independent from Fluxy's relationship with the End-User

4.2 No Data Processing Agreement (DPA) Required

Because Partner is NOT a Data Processor for Fluxy, a traditional Data Processing Agreement (DPA) is NOT required between Fluxy and Partner.
Why:

  • End-Users have a direct contractual relationship with Fluxy
  • Fluxy processes End-User data based on Fluxy's own Privacy Policy and Zero Box ToS
  • Partner only receives QR code images (public data)

What this means for Partner:

  • ✅ Simpler legal setup (no DPA negotiations)
  • ✅ No GDPR liability for End-User DPP data (Fluxy handles compliance)
  • ✅ No data breach notification obligations to Fluxy (Fluxy notifies End-Users directly)

Partner's ONLY GDPR obligation: Ensure your own privacy policy covers YOUR relationship with End-Users (for data YOU collect: billing, shipping, etc.). Do NOT claim to process End-User DPP data "on behalf of Fluxy".

Exception: White-Label Partnerships. If Partner requests white-label access (End-Users never see Fluxy branding), a DPA MAY be required. Contact legal@fluxy.one to discuss.

4.3 Required Disclosure to End-Users

Partner MUST disclose Fluxy integration at the point of DPP creation.
Minimum disclosure (Standard Integration):

"This QR code is powered by Fluxy.One. You will receive an email from Fluxy with access to manage your product data online. By proceeding, you agree to Fluxy's Terms of Service and Privacy Policy."

Recommended UX: Show disclosure text above "Generate QR Code" button. Include Fluxy logo (to set expectations for welcome email). Optionally link to Zero Box ToS and Privacy Policy.

What Partner should NOT do:

  • ❌ Claim that Partner is the DPP provider (Fluxy is the provider)
  • ❌ Promise features only Fluxy can deliver (e.g., "upgrade to Pro tier" — End-User must do this in Fluxy dashboard)
  • ❌ Collect consent "on behalf of Fluxy" (Fluxy obtains its own consent via email and dashboard login)

4.4 Data Location and Security

All End-User data is hosted by Fluxy in:

  • Google Cloud Platform, Belgium (primary)
  • EU-West (Belgium, Netherlands) (backup)

See Privacy Policy and Zero Box ToS for full details on security measures. Partner does NOT need to sign separate Data Processing Addendums or Standard Contractual Clauses (SCCs) unless Partner is located outside the EU and requests access to End-User data beyond QR code images.

5. REVENUE SHARE AND PAYMENT

5.1 Revenue Share Model (Confidential)

Primary Commercial Model: For most API Partners (including Avery and similar integrations), compensation is based on revenue sharing:

How it works:

  • Free DPPs (Zero Box Free Tier): End-Users who stay on the Free tier (100 QR codes, basic features) generate no revenue for either party. Fluxy covers hosting costs as customer acquisition strategy.
  • Paid Upgrades (DPP Light, Extended, Pro): When an End-User upgrades to a paid tier (DPP Light: €9.99/month, DPP Extended: €29.90/month, DPP Pro: €49.90/month), Revenue is split between Fluxy and Partner according to Commercial Appendix (confidential). Revenue share percentage is NOT disclosed in this Agreement (commercial secret).

Invoicing: Fluxy invoices End-Users directly (via Stripe, PayPal, Revolut Pay). Partner receives monthly payout based on revenue share. Payouts sent within 15 days of month-end via: Bank transfer (SEPA/SWIFT), Stripe Connect (if preferred), PayPal (upon request).

Reporting: Partner has access to real-time dashboard at https://partners.flxy.io showing: Number of Free vs. Paid End-Users referred by Partner, Monthly Recurring Revenue (MRR) from Partner's referrals, Breakdown by tier (Light, Extended, Pro), Revenue share amount (updated daily). Dashboard credentials provided after partnership approval.

Example (Illustrative Only — Actual Percentages Confidential): Partner integrates Fluxy form. 1,000 End-Users create DPPs via Partner's platform. 100 of them upgrade to DPP Light (€9.99/month). Monthly revenue: 100 × €9.99 = €999. Partner's share: [Confidential percentage] of €999. Fluxy's share: [Confidential percentage] of €999. Actual revenue share terms are defined in a separate Commercial Appendix, signed by both parties and marked confidential.

5.2 Alternative Model: Flat Monthly Fee (Optional)

Partners who prefer predictable costs instead of revenue share may request:

Fixed Fee Options:

  • Option A: Fixed monthly fee for unlimited DPP creation (white-label access)
  • Option B: Per-DPP pricing (for partners who want to resell DPPs under their own brand)
  • Option C: Custom enterprise pricing (for very high volumes or strategic partnerships)

When to choose flat fee: Partner wants to white-label DPPs (rebrand as their own service). Partner prefers fixed costs (no revenue volatility). Partner expects very high upgrade rates (flat fee may be cheaper).

To request flat fee pricing: Contact partnerships@fluxy.one

5.3 Payment Terms

Invoicing: Revenue share payouts issued monthly within 15 days of month-end. Minimum payout threshold: €50 (balances below €50 roll over to next month). Payment details collected during partnership onboarding.

VAT: EU Partners: Reverse Charge may apply (provide VAT ID). Non-EU Partners: 0% VAT (export services). Partner responsible for any local taxes in their jurisdiction.

Late Payments (if Partner owes Fluxy): If Partner is on flat-fee model and payment fails: Grace period: 7 days. After 7 days: API access suspended. After 30 days: Partnership terminated.

6. INTEGRATION AND ONBOARDING

6.1 Getting Started

Step 1: Partnership Application

  • Submit application at https://fluxy.one/api-partnership
  • Provide: Company details (name, registration number, VAT ID if EU), Expected volume (DPPs per day/month), Integration timeline, Primary contact for technical integration

Step 2: Approval and Commercial Terms

  • Fluxy reviews application (typically 2-3 business days)
  • Fluxy sends Commercial Appendix for signature (revenue share percentage, confidential)
  • Partner signs Commercial Appendix (DocuSign or wet signature)

Step 3: Technical Setup (1-2 weeks)

  • Fluxy provides: Embed code (iframe or JavaScript snippet), API credentials (for advanced integrations), Sandbox environment for testing (unlimited test DPPs), Technical documentation at https://docs.flxy.io, Dedicated integration support (Slack channel or email)

Step 4: Testing Phase

  • Partner integrates embed form in staging/dev environment
  • Create test DPPs, verify QR code generation
  • Test End-User email delivery and dashboard access
  • Verify revenue tracking in partner dashboard

Step 5: Go Live

  • Switch from sandbox to production API keys
  • Fluxy monitors first 100 DPPs for any issues
  • Dedicated support during launch week (priority response times)

Step 6: Revenue Tracking Activated

  • Partner dashboard activated at https://partners.flxy.io
  • Real-time revenue share reporting begins
  • First payout issued at end of first full month

No Upfront Costs:

  • Zero setup fees
  • Zero minimum commitments
  • Revenue share starts only when End-Users upgrade to paid tiers

6.2 Technical Support

During Integration: Email: api@flxy.io. Response time: 4 hours (business hours). Optional: Dedicated Slack channel for Enterprise partners.

Post-Launch: Email: api@flxy.io. Response time: 8 hours (business hours). Emergency contact (P1 issues): +371 26125210.

Documentation: Full API docs: https://docs.flxy.io. Integration guides: https://docs.flxy.io/guides. FAQ: https://docs.flxy.io/faq.

7. PARTNER RESPONSIBILITIES

7.1 Disclosure and Transparency

Partner MUST:

  • Disclose Fluxy integration to End-Users (Section 4.3)
  • NOT misrepresent the service (e.g., claim Partner owns DPP infrastructure)
  • NOT promise features Partner cannot deliver (e.g., ESPR compliance verification — only Fluxy provides this)

7.2 Brand Usage

Permitted:

  • "Powered by Fluxy.One" or "Integrated with FLXY.io" in marketing materials
  • Displaying Fluxy logo in integration documentation (subject to brand guidelines at https://fluxy.one/brand-guidelines)

Prohibited:

  • Implying Fluxy endorsement without written approval
  • Using Fluxy trademarks as part of Partner's own brand name
  • Modifying Fluxy logos (colors, proportions, taglines)

7.3 Compliance with Laws

Partner must:

  • Comply with all applicable laws in their jurisdiction
  • NOT use API for illegal purposes (counterfeit products, sanctioned goods)
  • NOT facilitate violations of GPSR, ESPR, or product safety regulations

Partner indemnifies Fluxy for claims arising from Partner's own business operations (e.g., Partner sells counterfeit labels, Partner violates local consumer protection laws).

8. INTELLECTUAL PROPERTY

8.1 Fluxy's IP

Ownership: Fluxy retains all rights to: FLXY.io API and underlying software, GS1 Digital Link infrastructure (https://dpp.flxy.io), API documentation, SDKs, embed code, Fluxy trademarks, logos, branding.

License to Partner: Partner may use API solely as authorized in this Agreement. Partner may NOT create derivative works or competing services.

8.2 Partner's IP

Ownership: Partner retains all rights to its own products, services, trademarks, branding.

No License Grant: Partner does NOT grant Fluxy any rights to Partner's IP (except for co-branding if requested).

8.3 End-User Data Ownership

Who owns DPP data?

  • End-Users own their product data (as per Zero Box ToS)
  • Fluxy has a license to host and display the data
  • Partner receives only QR code images (public data)

Partner has NO ownership rights to End-User DPP data.

9. LIABILITY AND INDEMNIFICATION

9.1 Limitation of Liability

Fluxy's Maximum Liability:

  • Capped at the revenue share paid to Partner in the 12 months preceding the incident
  • For pre-revenue partnerships (first 12 months): Maximum liability is €1,000

Exclusions: Fluxy is NOT liable for: Loss of revenue or business opportunities; Regulatory fines imposed on Partner; Partner's violations of laws or third-party rights; End-User claims (End-Users have direct recourse against Fluxy via Zero Box ToS); Third-party service outages (Google Cloud, Stripe).

No Consequential Damages: Fluxy is NOT liable for indirect, incidental, or consequential damages (lost profits, business interruption, reputational harm).

9.2 Force Majeure

Neither party is liable for delays caused by: War, terrorism, sanctions; Natural disasters; Internet backbone failures, DDoS attacks; Government actions (emergency laws, service shutdowns); Google Cloud outages, AI service disruptions.

9.3 Indemnification by Partner

Partner agrees to indemnify and hold harmless Fluxy from:

(a) Partner's Business Operations: Claims arising from Partner's products or services (e.g., Avery sells defective labels); Violations of consumer protection laws by Partner; IP infringement by Partner (unauthorized use of trademarks in Partner's own materials).

(b) Misrepresentation: Partner falsely claims to be DPP operator or ESPR compliance provider; Partner promises features Fluxy does not offer.

(c) Integration Issues: Partner embeds form in violation of these Terms (e.g., on illegal website); Partner facilitates creation of DPPs for prohibited products (Section 10).

Partner does NOT indemnify Fluxy for: End-User content (false data, IP infringement by End-Users); AI translation errors (covered under Zero Box ToS).

10. PROHIBITED USE

Partner may NOT use the API to facilitate:

  • Counterfeit products (fake certifications, unauthorized GTINs)
  • Illegal goods (weapons without licenses, controlled substances, sanctioned products)
  • Harmful content (products banned under GPSR, dangerous chemicals without warnings)
  • IP infringement (copying competitor DPPs, using unauthorized trademarks)

Consequences: Immediate API suspension; Partnership termination without refund; Reporting to authorities (if required by law).

11. TERM AND TERMINATION

11.1 Term

This Agreement begins on the date of API access and continues until terminated by either party.

11.2 Termination by Partner

Partner may terminate at any time: Send written notice to api@flxy.io (30 days' notice required); Cease all API usage and remove embed code.

Effect: No refunds for unused credits (if flat-fee model); Access to API terminated at end of notice period; End-User DPPs remain active (Fluxy continues to host them per ESPR obligations); Partner stops earning revenue share (existing End-Users remain Fluxy customers).

11.3 Termination by Fluxy

Fluxy may terminate immediately if: Partner violates this Agreement (prohibited use, misrepresentation); Payment failure exceeds 30 days (if flat-fee model); Partner engages in illegal activity; Partner's use threatens Fluxy's infrastructure (abuse, DDoS).

Notice: 7 days' notice for payment issues; Immediate suspension for security or legal violations.

11.4 Effect of Termination

After termination: Partner must cease all API usage; Partner must remove embed code from their platform; End-User DPPs remain active (Fluxy's ESPR obligation to host for 10+ years); Partner loses access to revenue dashboard; Final payout issued within 30 days (if balance ≥ €50).

12. CONFIDENTIALITY

12.1 Definition

"Confidential Information" includes: Commercial Appendix (revenue share percentage); Pricing terms, partnership agreements; API documentation, technical specifications; Business plans, integration roadmaps.

12.2 Obligations

Receiving Party must: Use Confidential Information solely for purposes of this Agreement; Protect it using industry-standard security (minimum: encryption); NOT disclose it to third parties (except employees/contractors under NDA).

Exceptions: Information already public; Required by law (court order, regulator request).

12.3 Duration

Confidentiality obligations survive termination for 5 years.

13. GOVERNING LAW AND DISPUTE RESOLUTION

13.1 Governing Law

This Agreement is governed by the substantive law of the Republic of Latvia.

13.2 Dispute Resolution

Step 1: Negotiation — Parties will attempt to resolve disputes amicably within 30 days.

Step 2: Mediation — If negotiation fails, mediation (costs split equally).

Step 3: Arbitration — If mediation fails, disputes resolved by arbitration under rules of Luxembourg Arbitration Association. Language: English. Seat: Luxembourg.

13.3 Exceptions

Either party may seek injunctive relief in court for: IP infringement; Data breaches; Unauthorized use of API.

14. MISCELLANEOUS

14.1 Entire Agreement

This Agreement, together with: Privacy Policy; Commercial Appendix (revenue share terms, confidential); Any executed Order Forms or Statements of Work constitutes the entire agreement between the parties.

14.2 Amendments

Fluxy may update this Agreement with 30 days' advance notice via email. Continued use of the API after the effective date constitutes acceptance. Commercial terms (revenue share percentage) cannot be changed unilaterally — requires mutual written agreement.

14.3 Severability

If any provision is found invalid, the remaining provisions remain in full effect.

14.4 Assignment

Partner may NOT assign this Agreement without Fluxy's written consent. Fluxy may assign to affiliates or successors with 30 days' notice.

14.5 No Waiver

Fluxy's failure to enforce any right does not constitute a waiver.

14.6 Language

The English version is authoritative. Translations are for convenience only.

15. CONTACT INFORMATION

API Support:
Email: api@flxy.io
Documentation: https://docs.flxy.io
Status Page: https://status.flxy.io

Partnerships & Commercial:
Email: partnerships@fluxy.one

Legal Questions:
Email: legal@fluxy.one

Data Protection Officer:
Email: dpo@fluxy.one

Registered Address:
SIA Fluxy One
Rupniecības iela 16-14B
Riga, LV-1010, Latvia
Reg. No. LV40203559086

END OF API PARTNERSHIP TERMS

Logo Fluxy.One‍‍‍
Turn regulation into new opportunities!
Saas Webflow Template - Charlotte - Designed by Azwedo.com and Wedoflow.com
Saas Webflow Template - Charlotte - Designed by Azwedo.com and Wedoflow.com
Saas Webflow Template - Charlotte - Designed by Azwedo.com and Wedoflow.com
Saas Webflow Template - Charlotte - Designed by Azwedo.com and Wedoflow.com
Free consultation
About
Blog
International:
Uzbekistan
Features
{SMB Solution}
Industries:
Textile DPP
Electronics DPP
Furniture & Mattresses DPP
Steel & Iron DPP
Toys DPP
Building Materials DPP
CE Marking / GPSR Compliance
Legal:
Privacy Policy
Cookie Policy
Website Terms of Services
Platform Terms of Services
ZeroBox Terms of Services
API Terms of Services
Cookie Settings
Made with ♻️ in Europe! Based on the FLXY.io platform.
©2026 SIA Fluxy One. All rights reserved.
LV40203559086 | PIC: 877411658 | D-U-N-S®: 965808875
+
Let’s make compliance simple together.
Our team will reach out within 1 business day with your personalized DPP offer and onboarding details. Let’s simplify compliance - together.
Oops! Something went wrong while submitting the form. Please try again or contact us at info@fluxy.one