Five marketplaces.
One back office.

We built a shared back office for sellers on Amazon, eBay, Etsy, eMAG and Allegro. Stock, orders, buyer messages, returns and payments are connected in one multi-tenant platform.

E-commerce seller platform

Client project, in production

Multi-tenant web application

4 months

from development to production

Five channels.
The same last unit.

One physical stock pool, five APIs with different limits and delays. We brought inventory and the seller’s daily work into one product.

What Cursopic built

The integrations underneath.
The workspace on top.

For owners, operations,
support and finance.

Five marketplace integrationsOrders, listings, messages and returns behind a shared model.

A central inventory ledgerReservations, channel queues and a path for stock conflicts.

The seller’s daily workspaceOrder processing, AI-assisted replies, return rules and payment tasks.

Reserve in one place.
Update at each channel’s pace.

The ledger holds the stock the platform can reserve. Marketplace listings receive updates through separate queues, so a central reservation and an external stock update are different steps.

  1. Incoming order

    Bring marketplace orders into one model, even when channel data and order states differ.

  2. Atomic ledger reservation

    Record the order once and reserve its SKU’s warehouse stock in the same atomic operation. Two orders cannot reserve the ledger’s last unit.

  3. Channel update queues

    Send the latest quantity through each channel’s own queue, at the pace its API allows. Zero-stock updates go before routine changes.

The last unit
changes the priority.

Zero goes first.

Zero-stock updates go ahead of routine changes in each channel’s queue.

A late order has a path.

The demo resolves it through another warehouse. An allowed backorder or cancellation are alternatives.

Built for the gaps
between systems.

External APIs will not move in lockstep. Buffers, reconciliation and channel-specific connectors make those differences part of the product.

  • Room for API delays.

    A stock buffer lets slower channels list a little less than the ledger holds.

  • Drift gets corrected.

    Scheduled reconciliation compares channel listings with the ledger and corrects missed updates.

  • One seller workflow.

    Connectors absorb each API’s rules. Sellers keep the same order statuses and actions.

From dispatch
to the buyer’s next question.

One workspace connects the order, its deadline and the conversation around it. Operations and support work from the same context.

One order flow.

Shared statuses, dispatch deadlines, bulk actions and labels. Updates go back to the right marketplace.

AI drafts. A person sends.

Order details and past answers inform the draft. A support agent reviews, edits and sends the reply.

Returns follow
the seller’s rules.

Each seller defines which returns qualify for an automatic refund. Other cases go to a person for review.

From rule to refund.

The example shows a return matching a seller’s rule, followed by a Stripe refund.

Payments were part of the build.

We integrated Stripe for the project’s payments, refunds, payouts and platform subscription billing.

Four months.
One connected product.

Our development team built from inventory correctness outward: the ledger and connectors, then the workflows sellers use every day.

  • 4months to production

    From connectors to launch.

    Inventory, marketplace integrations, order processing, buyer messaging, returns and payment tasks came together in the multi-tenant platform.

  • One core.
    Many sellers.

    Built around the ledger.

    Java, Spring Boot and PostgreSQL underpin the platform, with Kafka and Redis. Docker and Kubernetes support the production deployment.

One operation.
A different working day.

Results from the project account,
with seller outcomes in context.

500,000+

Orders processed per day.

Across all sellers on the platform.

Platform-wide volume
About40%

Less time from order to dispatch.

Time saved in processing and shipping an order.

Up to$7,000

Saved on support per month.

Per seller; the upper reported figure.

50%

Growth in monthly revenue.

Reported by some stores on the platform.

These figures describe the client project and reported seller outcomes.

Let’s build your next advantage

Tell us what you want to launch, improve or automate. Let’s discuss the scope and the next step.

Get in touch

Prefer email?

sales@cursopic.com

Cursopic

Tell us about your project

What would you like to launch, improve or automate? A few lines are enough to start.

We use what you send only to reply to you about your request. Privacy policy (opens in a new tab)

Prefer email?

sales@cursopic.com