Terms of Service

Beyoğlu Professional is designed primarily for professional and commercial users, including Producers, exporters, importers, distributors, marketplace sellers, dropshippers, e-commerce merchants and other businesses operating in or selling into European markets.

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

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

The platform can automate calculations, workflow and declarations. It cannot make incorrect source data true.

The customer must provide information that is complete, current and accurate to the level reasonably required for the relevant compliance operation. This can include 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 request 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 when a parcel is entered into the relevant national compliance ledger. We charge the compliance event, not an unfulfilled shopping-cart event.

An order cancelled before shipment that 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. Any 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 authority, PRO or system finally collects payment. The platform may therefore calculate and reserve an expected regulatory amount as covered shipments enter the relevant country ledger.

This reserve does not mean that PPWR itself requires every Producer to prepay Beyoğlu on the date of shipment. It is an operational risk-control mechanism intended 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 payment service provider, safeguarded client-money arrangement or another legally appropriate third-party payment structure. Regulatory money must remain distinguishable from Beyoğlu Professional's service revenue and working capital.

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. Automation does not transfer responsibility for source-system accuracy.

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 must not knowingly be 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.

Generated, submitted, registered and approved are different statuses.

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 record should show the actual status reached in the national process.

Compliance files may contain commercially sensitive information. 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 or processor arrangement. Security practices are described in the Data & Security Policy.

Ending a software or commercial relationship does not automatically deregister a Producer or terminate a statutory mandate.

Termination must be distinguished from the legal steps required to end an EPR Authorised Representative 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 Authorised Representative 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 or restricts liability that cannot lawfully be excluded or restricted under applicable law.

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