Enterprise
We won eBay's pitching contest in March 2026 and are scoping a pilot. ANWB's go-live is agreed. Other enterprise conversations are underway. Enterprise adoption of Forwarding is happening. Here is what it looks like.
What we bring
What we ask from you
Why this deserves boardroom attention
30 to 40 percent of online fashion purchases are returned. For a retailer at €50M annual GMV, that is €15M to €20M of returned product moving through reverse logistics every year. At 20 to 65 percent processing cost, the return P&L line is now too large to manage as overhead.
CSRD reporting is in force. PPWR begins August 2026. Empowering Consumers enforcement starts September 2026. ESPR phases in textile destruction limits through 2026 and 2027. Returns sit at the intersection of all four, and "we'll handle it later" is now a 12-month problem, not a 5-year one.
Retailers who restructure returns ahead of regulation gain a measurable cost advantage and a credible sustainability story for CSRD reports. Those who wait for the deadline retrofit under pressure. Forwarding turns a compliance obligation into a P&L improvement and a defensible ESG narrative.
This is why returns now appear in C-level agendas at retailers our team works with. The conversation has shifted from "how do we process returns more efficiently" to "how do we change the model entirely." What follows is what working with Forwarding looks like at enterprise scale.
Forwarding works the same way for a 500-order-per-month retailer as it does for a 500,000-order-per-month marketplace. The algorithm, the return portal, the consumer experience: these are identical. What changes is everything around the integration: the procurement process, the legal review, the integration complexity, the SLA requirements, and the level of support needed during and after go-live. We have built an enterprise track that addresses each of these. It is not a premium tier of the same product. It is a different engagement model designed around how enterprise procurement and IT actually work.
We designed Forwarding for enterprise scale from day one. The matching algorithm is a Markov Decision Process that scales linearly with listing count, with the methodology independently validated, not a hand-tuned heuristic. The infrastructure runs on Google Cloud with EU data residency, auto-scaling, and 99.9% uptime guaranteed (99.95% on enterprise SLAs). The REST API is rate-limited per retailer with dedicated throughput allocation for enterprise clients. Winning eBay's pitching contest in March 2026 is the external signal that the architecture is being taken seriously at marketplace scale.
A named contact at IGF who owns the relationship, not a support queue. Available for calls, responsive to Slack, accountable for your results.
Standard SLA: 99.9% uptime, 4-hour response for critical issues. Enterprise SLA: negotiated based on your requirements, with uptime guarantees, response windows, escalation paths, and penalties agreed in writing.
Enterprise stacks are complex: multiple ERPs, WMS systems, custom return portals, and compliance requirements. We scope custom integrations with your IT team and support them throughout. No hand-off to documentation.
Security questionnaire responses, DPA signed before contract, sub-processor list with legal basis, CO₂ methodology documentation, and insurance details: ready for your procurement team without scheduling a call.
Monthly and annual impact reports formatted for CSRD and sustainability reporting. Per-category breakdown of Forwards, savings, and CO₂. Exportable in formats your finance and ESG teams can use directly.
Forwarding works across borders: the algorithm resells items in the country they are shipped to, reducing cross-border logistics and duty costs. Multi-language consumer interface (EN, NL, DE) included. Additional markets on request.
Enterprise onboarding follows a different path from SME pilots. Here is what to expect.
We review your platform stack, return volume, product categories, and existing return infrastructure. We identify integration complexity and confirm whether Forwarding is a fit. We present a preliminary ROI estimate based on your numbers.
We provide all documentation your legal and procurement teams require: DPA, security questionnaire response, sub-processor list, SLA terms, and insurance details. We respond to follow-up questions within 24 hours. Most procurement reviews complete in 2 to 4 weeks.
Your IT team and ours map the full integration. We produce a written integration plan covering API endpoints, webhook configuration, ERP/WMS touchpoints, consumer flow, email customisation, and testing approach. No surprises in implementation.
Enterprise integrations typically run in two phases: a manual pilot on a subset of SKUs or markets (4 to 6 weeks), followed by full automation. Each phase has defined acceptance criteria and sign-off before proceeding.
Every enterprise client gets a named account manager from the IGF co-founding or senior team (currently Carl van Heijst, Pepijn Stribos, or a senior hire when the team grows), not a CSM rotating through tickets.
Standing cadence
Response commitments
Proactive monitoring
The following organisations have agreed a go-live or selected It Goes Forward in a competitive process. Other enterprise conversations are underway but we name companies publicly only once they reach pilot-signed, onboarding, or live stages.
eBay is one of the world's largest online marketplaces, with hundreds of millions of active buyers globally and one of the largest flows of fashion returns in e-commerce. In March 2026, Forwarding won eBay's pitching contest. The next step is to scope a pilot with eBay; the exact shape of that pilot is being worked out now.
For an enterprise buyer, the inference still matters: a marketplace processing this volume of returns would not select a technology through a competitive contest if it had doubts about scale readiness. Winning the contest is our most substantive signal so far that Forwarding is being taken seriously at marketplace scale.
Pilot scope and terms are TBD. Results will be published where eBay permits once a pilot is defined and complete.
Major Dutch membership organisation and retailer. Tech approach agreed, integration in progress.
Status as of April 2026. Other enterprise conversations are underway; we name companies publicly only once they reach pilot-signed, onboarding, or live stages.
Enterprise procurement and legal teams have specific documentation requirements. We have these ready and respond to follow-up questions within 24 hours.
Full security details: Security & Privacy →
Regulatory compliance: EU Compliance →
We have had the 'what would it need to cost to make sense for you' conversation with every enterprise client so far, and found a number in every case.
Enterprise pricing is tiered by Forward volume: the more you Forward, the lower the per-Forward fee. The monthly platform fee is fixed and scales with complexity (multi-market, multi-ERP, dedicated infrastructure). There is no setup fee, no integration fee, no annual lock-in. We do not publish enterprise pricing because it genuinely depends on volume, integration scope, and required support level. The right conversation is: what does your return volume look like, and what would Forwarding need to cost for the economics to work?
Enterprise buyers have learned to ask about failure cases. Here is how we answer the three we hear most often.
Forwarding is charged per completed Forward, not per integration month. Low adoption means low fees. We share responsibility for adoption: our team optimises the consumer messaging, the discount ranges, and the eligibility rules with yours during the first quarter. If we cannot reach a level of adoption that is economically meaningful for you (typically 20%+ sender adoption), we acknowledge that and discuss either changes in scope or early termination without penalty.
Your integration is built on REST API and OpenReturn, our open-source protocol (Apache 2.0). The specification and reference implementation are public. If IGF ceases operation, your integration does not become a dead dependency: you can continue running on the open protocol with another implementer, or self-host the reference portal. Your consumer data is covered by the DPA: breach notification, exit data export, and deletion are contractually guaranteed.
Integration failure has a bounded downside: Forwarding is additive. Your existing return flow continues to operate unchanged. Returns that don't Forward (because of integration issues, low match rates, or consumer choice) route through your warehouse as they do today. Worst case: you paid platform fees during a pilot that did not generate enough Forwards. You did not disrupt your existing return operations.
Legal and procurement review typically takes 2 to 4 weeks from first documentation request to signed agreement. This assumes we respond to all queries within 24 hours, which we do. Integration planning and implementation follows after signature.
Yes. We have experience integrating around WMS systems; conventional warehouse flows remain unchanged. We send webhook events that your OMS or ERP can consume directly. We have documented implementations for Microsoft Dynamics 365 Business Central, and adapter interfaces for generic ERP integration. Bring your IT team to the scoping call and we will map the integration together.
We integrate via REST API into any return flow that supports webhooks. We have done this for Returnless and Bleckmann; we can do it for your portal. Custom integration is scoped in writing before implementation begins.
Yes. Forwarding is additive: it sits on top of your existing return infrastructure. Items that are not matched, not eligible, or where the consumer chooses the conventional option continue through your existing return flow unchanged.
Yes. We can arrange a reference call with Kuyichi for enterprise prospects who are seriously evaluating. We ask that reference calls happen after initial scoping, so both sides' time is used well.
We typically engage enterprise clients with 2,000+ returns per month. Below this, the SME pilot path (monthly contract, self-serve onboarding) is more appropriate. At 2,000+ returns per month, the economics of a dedicated integration and account management are justified for both sides.
Dutch law. Rotterdam jurisdiction. It Goes Forward B.V. is a Dutch entity; our standard agreement is governed by Dutch law with disputes resolved in Rotterdam courts. For enterprise clients, we are open to negotiating governing law and forum; we have done so for US and UK enterprise conversations. Contact our legal team through your procurement contact and we will scope accordingly.
Yes. Most enterprise engagements begin with a paid pilot, typically 3 to 6 months, scoped to one product category or one market. Pilot terms include platform fee + per-Forward fee, no integration fee, defined exit criteria. At the end of the pilot, either side can continue or terminate without penalty. Several of our current enterprise conversations are at the pilot-scoping stage.
Enterprise conversations start with a scoping call. 60 minutes, your IT lead and ours, no commitment required, and you leave with deliverables you can take back to your team.
What we bring
What we ask from you
Or send your procurement questionnaire to hello@itgoesforward.com with subject line "Enterprise"; we respond within 24 hours.
