> For the complete documentation index, see [llms.txt](https://docs.violet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violet.io/ecom-platforms/rithum.md).

# Rithum

Rithum (formerly CommerceHub) is a B2B marketplace and drop-shipping platform that connects suppliers with retailers. Unlike direct-to-consumer storefronts, Rithum operates as a fulfillment network — merchants are suppliers who fulfill orders placed through retail channel partners.

> **Partner requirement**: Rithum is a partner-gated integration. To enable Rithum for your Violet application, you must first become a registered Rithum partner. Contact Violet support to initiate the partner enablement process once your Rithum partnership is established.

## Connection

Rithum does not use a standard Violet Connect onboarding flow. There is no OAuth redirect or credential form presented to the merchant. Instead, connection and authentication are managed through the Rithum partner relationship — credentials are provisioned externally and configured at the platform level.

Merchant profiles are fetched via the Rithum site profile API once the integration is active.

## Order Status

Rithum uses a three-tier status model that maps independently to Violet's order lifecycle:

| Rithum Status Type  | Description                                             |
| ------------------- | ------------------------------------------------------- |
| **Checkout status** | Whether the order has been acknowledged by the supplier |
| **Payment status**  | Payment state of the order                              |
| **Shipping status** | Fulfillment and shipment state                          |

Violet reconciles these three status dimensions into a unified order and bag state.

## Products

Rithum supports the following product types:

| Type               | Description                                                 |
| ------------------ | ----------------------------------------------------------- |
| `VARIATION_PARENT` | Parent product grouping variants (not directly purchasable) |
| `STANDARD`         | Standard physical product                                   |
| `DIGITAL`          | Downloadable or digital product                             |
| `BUNDLE`           | Bundle of multiple products                                 |

`VARIATION_PARENT` items are treated as offer containers and are not directly purchasable — child variants are exposed as SKUs.

## Discounts

Rithum does not have a native discount or coupon code system. Discounts are applied as negative line-item values using Rithum's `additionalCostOrDiscount` field. Custom discounts (fixed or percentage) are supported; synced promo codes are not.

## Shipping

When the requested shipping method cannot be matched to an available Rithum shipping option, Violet falls back to the first available shipping method configured on the supplier's account.

## Notable Behavior

* **No standard auth flow**: Onboarding is managed through the Rithum partner relationship rather than Violet Connect.
* **Drop-shipping model**: Rithum merchants are suppliers fulfilling orders on behalf of retail partners, not direct-to-consumer storefronts.
* **Order acknowledgment**: Orders must be acknowledged by the supplier (reflected in checkout status) before fulfillment proceeds.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.violet.io/ecom-platforms/rithum.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.