Audience: Retailers

This guide is meant to help retailers get started with Rithum. If you are a retailer that is new to Rithum then review this guide and the attached step-by-step walkthroughs. 

Step 1: Welcome to Rithum

Your first step when connecting to Rithum is to verify that your account is configured correctly. Please review the links below for help setting up your ship mapping, creating additional user accounts, and making sure that your company information is correct:

Ship Mapping: Setting up Ship Mapping

User Accounts: Creating Additional User Accounts

Company Information: https://app.dsco.io/account/company

Rithum EDI Information: EDI for Retailers

As you read through the steps below you'll notice several references to creating automated jobs in Rithum. Rithum uses a simple automation system to exchange data with you and your suppliers. If you have no intention of using automation with Rithum and only plan on using the web application then you can safely ignore those instructions. 

Step 2: Checking inventory

The first part of the testing process is to verify that you can see your supplier's inventory in the platform. A good first step to take is to head to the Inventory page and verify that you can see inventory for a specific supplier. For help viewing your supplier's inventory in the web application, see Viewing inventory in the web application.

For more information on setting up an automated job to export inventory from the platform, see Creating automated export jobs.

Step 3: Creating orders

Once you've verified that you can see and export your supplier's inventory, go ahead and submit some test orders for that inventory. Rithum's recommendation is to submit three different orders to test several different shipping scenarios:

Test Order #1: Have the supplier completely ship this order. 

Test Order #2: Have the supplier partially ship/cancel this order.

Test Order #3: Have the supplier completely cancel this order.

Each test order should have multiple (at least two) SKUs included on the order so that the supplier can correctly test the partial ship/cancel scenario. 

For more information on creating those orders in the web application, see Creating an order.

For more information on creating an automated job to import your orders to the platform, see Creating an automated order import job

Step 4: Checking shipped orders

Once your supplier has acknowledged and shipped your test order, the next step is to test that you can view those order updates in the platform For more information on checking for those shipping updates, see Checking shipping updates.

If you're using automation in Rithum, make sure that you've already set up your shipment export job. For more information, see Creating automated export jobs.

Step 5: Checking cancelled orders

Along with checking that a supplier has shipped an order, you should also check to verify that the supplier cancelled an order as well. For more information, see Checking cancelled orders.

If you're using automation in Rithum, make sure that you've already set up your cancellation export job. For more information, see Creating automated export jobs

Step 6: Working with invoices

Your suppliers may also want to send their invoices to you via the platform. Your onboarding process should involve checking those invoices to verify that they include all of your required information. For more information, see Viewing your suppliers' invoices.

If you're using automation in the platform, make sure that you've already set up your invoice export job. For more information, see Creating automated export jobs

Step 7: Celebrating

Once you've finished your invoice testing then you are done with your onboarding to Rithum. Go ahead and work directly with your suppliers to determine a go-live date when you will start submitting live orders to Rithum. Then go buy some milkshakes! Finishing an onboarding process, even one as simple as this, deserves some attention!

Was this article helpful?
2 out of 3 found this helpful

Comments

0 comments

Please sign in to leave a comment.