Skip to main content
Build the future with Agentforce at TDX in San Francisco or on Salesforce+ on March 5–6. Register now.

Configure Tax, Fulfillment, and Data Import

Learning Objectives

After completing this unit, you’ll be able to:

  • List the steps you need to take to configure gross tax display in Order Management.
  • List the three fulfillment type categories.
  • Explain how hold fulfillment order capacity works.
  • Explain how status category relates to a fulfillment order record’s status.
  • Describe how you can import order records.

Configure Settings

Order Management is tightly integrated with fulfillment processing features and price, tax, and order status data. That means more settings. So Linda Rosenberg, the admin, learns how to configure these features in Order Management.

Configure the Tax Display

Linda wants to configure price and tax display in her org, which depends on the taxation type used by a locale: net or gross. Here’s what you need to know.

Taxation Type

Example

Prices and Taxes Display

If You Only Do Business with a Net Tax Locale

Net 

Sales taxes and  prices

Separately

No extra configuration required.

Gross

Value-added tax (VAT)

Combined

Configure your org’s page layouts to display amounts that combine prices and taxes.

Linda’s org is enabled for multiple currencies, so she creates a user profile for service agents in gross tax locales by cloning the standard user profile. Then she creates page layouts that use gross tax fields instead of net tax fields, and assigns them to the new profile. Here’s how she does it.

  1. From Setup, in the Quick Find box, enter Object Manager, and then select Object Manager.
    • For each object that displays prices, create a page layout that uses gross taxation fields that combine prices and tax amounts.
  1. From Setup, in the Quick Find box, enter Profiles, and select Profiles.
    • If your org is enabled for multiple currencies, clone the Standard User profile. Give the new profile a name that identifies it as applicable for users working with gross tax.
    • If you only do business in a locale that uses gross taxation, edit the Standard User profile.
    • If your org is enabled for multiple currencies, edit the new profile.
    • Assign the gross taxation page layouts to the user profile.
  1. Create at least one Order Summary record.
  2. In Salesforce Order Management, open any Order Summary record details page.
    • From the Setup menu on that page, select Edit Page.
    • Configure the Fields for the Gross Tax Orders section of the Totals component.
    • Save and activate the page.

Configure Fulfillment

The fulfillment part of the order process handles how an order reaches the shopper. This always involves a location and a status. Order Management comes with sample fulfillment packages that include flows, processes, and Apex classes that show you how to implement fulfillment with Flow Builder.

Fulfillment Categories and Types

Fulfillment types are how an order is fulfilled, such as from a warehouse or online. Order Management handles this with flexible fulfillment types that are each assigned to a fixed fulfillment type category. Order Management comes with default fulfillment types, and you can add more. The fulfillment type that’s assigned to a fulfillment order denotes the fulfillment method that Order Management uses for the products in that order. Here are the categories and types.

Fulfillment Type Category

 Default Fulfillment Types

Physical

  • Warehouse
  • Retail Store
  • In Store Pickup

Drop Ship

  • Supplier

Digital

  • Download
  • Email

While Linda can’t modify fulfillment type categories, she can customize fulfillment types as long as she associates each with a fulfillment type category. To customize fulfillment types, she edits the picklist values for the Type field on the Fulfillment Order object.

Fulfillment Locations

Where exactly do those products come from? That would be the fulfillment location. Linda defines a set of fulfillment location types, such as Warehouse and Retail Store, and adds them to the Location Type picklist on the Location object. Then she creates a location record to represent each of her fulfillment locations.

She can also create a location ranking system by using the priority in her routing logic. She does this by adding values to the Location object’s Priority field picklist and assigning a value to each location. This doesn’t happen automatically.

She can limit the number of fulfillment orders assigned to a location by defining its fulfillment order capacity. How many fulfillment orders can be assigned to a location? The Location object has three fields for working with fulfillment order capacity.

Location Object Fields

Description

Track Fulfillment Order Capacity

Whether the location’s capacity is tracked.

Fulfillment Order Capacity

The maximum number of fulfillment orders that can be assigned to the location per user-defined duration.

If the value is null, the location’s capacity is unlimited.

Assigned Fulfillment Order Count

The number of fulfillment orders currently assigned to the location.

To define the time period associated with the maximum capacity, reset this value at a certain interval. For example, to track capacity per day, run an automated job that sets this value to 0 for each location at midnight of the location’s time zone.

Keeping track of what’s available to ship from a location is important for on-time delivery and shopper satisfaction. Order Management handles a location’s capacity via actions on fulfillment order capacity data, as shown in this table. Order Management can hold, confirm, release, and get a location’s fulfillment order capacity.

Resource/Action

Description

Hold Fulfillment Order Capacity

To assign a fulfillment order to a location, hold capacity for it at the location. When the location has no free capacity, it returns an error. Free capacity is the location’s fulfillment order capacity minus the sum of its held capacity and assigned fulfillment orders.

Confirm Held Fulfillment Order Capacity

When you assign a fulfillment order to a location, confirm the held capacity for it at that location.

This increases the location’s assigned fulfillment order count and decreases its held capacity.

Release Fulfillment Order Capacity

If you hold capacity for a fulfillment order at a location, and decide not to assign that fulfillment order to that location, release the held capacity.

This decreases the location’s held capacity without increasing its assigned fulfillment order count.

Get Fulfillment Order Capacity Values

Getting the values returns a location’s maximum capacity, assigned fulfillment order count, and capacity being held. This is the only way to retrieve the held quantity, because it isn’t represented by a field on the Location object.

Changing the assigned Fulfillment Order Count doesn’t remove held capacity for unassigned fulfillment orders. To decrease held capacity, you must confirm or release it.

To use Salesforce Omnichannel Inventory to manage inventory locations, create location groups and assign locations to them. Set the ShouldSyncWithOci field to true for locations and location groups that are part of your Omnichannel Inventory implementation.

Explore Status and Status Categories

Order Management uses status categories to track orders as they make their way through a workflow. When Order Management sets a fulfillment order record’s status, it’s also setting its status category.

You can’t change status categories. They are fixed. You can, however, customize a status as long as you associate it with a status category. Fixed status categories are important if you have custom processes that depend on a record’s status category.

The status category of a fulfillment order drives the quantity fields on the order product summaries that are associated with its fulfillment order products. For example, when a fulfillment order record has the Assigned or Pickpac status, the status category is Fulfilling. You can add order statuses based on your business processes, such as:

  • Approved
  • Waiting to Fulfill
  • Delayed

So how does this work with Order Management? Order Management works with multiple object types, as shown in this table. Each object type has fixed status categories, each of which is associated with one or more statuses. Here’s how they are configured out of the box.

Object Type

Status Category

Default Statuses

Fulfillment Order

Draft

  • Draft

Activated

  • Activated

Fulfilling

  • Assigned
  • Pickpack

Closed

  • Fulfilled

Canceled

  • Canceled

Order

Draft

  • Draft

Activated

  • Activated

Order Summary

N/A

  • Created

Process Exception  

Active

  • New
  • Triaged

Inactive 

  • Ignored
  • Paused
  • Voided

Resolved

  • Resolved

Resolved

Activated

  • Activated
  • Submitted

Canceled

  • Canceled

Closed

  • Closed

Draft

  • Draft

The Order Summary object has a Status field, but not a Status Category field. Standard Order Management functionality doesn’t use order summary statuses, though you can use them to implement custom business processes. If you add order summary statuses, we recommend that you configure them to match order statuses.

Import Historical Order Records

Typically, order data comes in through high-scale orders and order summaries are created automatically; although, a user can trigger order summary creation by manually importing a pending order summary.

When Linda needs to import historical or non-standard order records, she does this via the bulk or composite API and configures the Create Order Summary flow to run on the imported order records.

The API is a developer tool, requiring her to get help from a developer; so she uses Flow Builder to get started. It’s important to use Flow Builder or call the API, and not create OrderSummary records directly. Automating order processing saves time and reduces data errors. To import large amounts of order data, Linda asks a developer to help her with Bulk API 2.0. When importing small amounts of order data, they can make composite REST API requests.

After Linda starts using Order Management in production, she can import historical order data from a legacy system for reference purposes. Typically, for orders that are no longer subject to servicing, she imports them as unmanaged orders.

Next Steps

In this unit, you learned how to configure price and tax display, fulfillment, order status, and import historical or non-standard order records. Next, learn how to configure payment processing.

Resources

Comparta sus comentarios de Trailhead en la Ayuda de Salesforce.

Nos encantaría saber más sobre su experiencia con Trailhead. Ahora puede acceder al nuevo formulario de comentarios en cualquier momento en el sitio de Ayuda de Salesforce.

Más información Continuar a Compartir comentarios