Terms of Service

The service is intended primarily for Producers, exporters, importers, distributors, marketplace sellers, dropshippers, e-commerce merchants and other business users.

A person using the service for an organisation represents that they are authorised to provide information and instructions on behalf of that organisation to the extent required for their activity.

Nothing in these Terms removes mandatory consumer rights if a person is legally entitled to such rights despite the service's B2B positioning.

The customer must provide information that is complete, current and accurate to the level reasonably required for the relevant compliance operation.

This includes, where relevant, legal-entity information, Producer status, products, packaging materials and weights, suppliers, fulfilment routes, marketplaces, destination countries, parcel quantities and reporting-period information.

The customer must notify Beyoğlu of material changes without waiting for the next statutory declaration.

We may ask for supporting evidence, including specifications, invoices, registration documents, packaging records or other information reasonably necessary to test the consistency of the data supplied.

Where information appears materially unreliable, Beyoğlu may refuse to process it, route the matter for review, request correction or suspend the affected operation.

The standard parcel fee applies to a parcel entered into the relevant national compliance ledger.

An order that is cancelled before shipment and never becomes a reportable parcel does not create an ordinary declared-parcel fee.

Multiple products shipped in one declared parcel create one parcel fee. One order divided into several separately declared parcels creates one fee for each declared parcel.

A later commercial return does not automatically erase the original regulatory event. Regulatory adjustment follows the applicable national reporting and system rules rather than a generic e-commerce refund rule.

A regulatory obligation can accumulate before the date on which the authority, PRO or system finally collects payment.

The platform can therefore calculate and reserve an expected regulatory amount as covered shipments enter the relevant country ledger.

This reserve is not a representation that PPWR itself requires every Producer to prepay Beyoğlu on the date of shipment. It is an operational risk-control mechanism designed to ensure that funds are available when the actual regulatory payment falls due.

Where customer regulatory money is held pending payment, the intended architecture is a licensed PSP, safeguarded client-money arrangement or another legally appropriate third-party payment structure.

Regulatory money must remain distinguishable from Beyoğlu Professional's service revenue.

If sufficient regulatory funding is unavailable, Beyoğlu may suspend or restrict the affected compliance operation where continuing would create an unfunded payment obligation or conflict with an accepted regulatory mandate.

Customers may transmit data through an API, webhook or another supported integration.

The customer remains responsible for ensuring that the source system sends the correct order, parcel, destination, SKU, quantity and packaging information.

API credentials must be protected and may not be knowingly exposed in public code or shared with unauthorised persons.

Beyoğlu may apply duplicate detection, validation, rate limits, authentication controls and exception routing to protect data and regulatory integrity.

An integration event that can materially change the legal result — for example a new Member State, a new packaging profile or a change from B2C to reseller supply — may be prevented from flowing through ordinary automation until the exception has been reviewed.

Beyoğlu tools and templates can prepare structured registration applications, reporting files, mandates, evidence packs and other compliance records.

A generated document has not necessarily been submitted. A submitted document has not necessarily been accepted. A registration application is not a registration number. A prepared mandate is not proof of authority acceptance where such acceptance is required.

The relevant evidence file should record the actual status reached in the national process.

Each party must use reasonable care with confidential business and regulatory information received through the relationship.

Personal-data processing is additionally governed by the Privacy Policy and, where applicable, a Data Processing Agreement or other controller arrangement.

Termination must be distinguished from the legal steps needed to end an EPR AR mandate, close a PRO relationship, deregister a Producer, reconcile a final report, pay outstanding regulatory charges or preserve required historical evidence.

Those steps are handled according to the applicable country rules and engagement documents.

A public information page, a software tool and a statutory EPR AR mandate do not create the same level or type of legal responsibility.

The applicable Order Form, mandate and governing law determine the specific allocation of responsibilities and any agreed contractual limitations.

Nothing in these general Terms excludes liability that cannot lawfully be excluded or restricted under applicable law.

Public legal information and tools remain subject to the Regulatory Disclaimer .