Inventory
Items
Before you create items, you'll want to set up locations and layouts in your dashboard so that you'll be able to add inventory levels for the item.
Your inventory for items is tracked in a property called levels
, which will give you information about the location and optionally the layout the item is in.
Create Item
The only property you need to create an item is name
, by which this item will be searchable. However, we recommend adding a few more properties:
Example
Update Item
You can update an item by using its ID.
When updating inventory, you increment and decrement quantities by passing in positive and negative integers.
You can reset a value by passing the integer inside of an array as shown in the example below. It's not recommended to reset values, since incrementing and decrementing will get you the same result, but this is an escape hatch if you need it and thus the ergonomics of an array prevent accidental usage of an otherwise potentially dangerous feature.
Lastly, you can optionally provide a layout value to be more specific about the item's exact whereabouts in that location. If the item already has a layout associated with it, it will keep adding to that layout unless you explicitly tell it not to. The best rule of thumb is either use layouts for everything, or don't use them at all.
Example
Retrieve Item
Get a single item using its id
.
List Items
Example
When you want to retrieve multiple items, your data
property on the result will always be an array
even if you don't have any items.
Pagination
If the has_more
property on the pagination object is set to true, you know there are more items in the database that have not been returned to you. The pagination object also has a page
property indicating your current offset and a limit property. The total_count property in pagination returns the the total number of items in the database.
By default the page
is set to 1
and the limit
is 25
.
If we want to query for items 26 - 50, we would request page 2 with a query parameter.
Filter
You can filter items by location_id
- location_id - Add the ID of one of your locations to get all of the deliveries currently mapped to that location. For example:
location_id=loc_czhgjrk5JaVvyATPDbyURp
Sorting
Sorting describes in what order you want your responses to come in. You can select an available property by which to sort, as well as the direction.
- order_by - The property by which to sort. Available properties are:
created_at
,name
- direction - The direction to sort. Available directions are:
asc
anddesc
By default, items will be sorted by in ascending order by name, meaning they are returned alphabetically.
Search
There are times when filtering is not enough and you want to find a specific item by some other attribute, typically by name, SKU, or GTIN. In this case, you can do a fuzzy, typo-tolerant search of every item in the database. Below are the item properties that are supported by our full text search. The properties follow the same schema as the actual item model, just with a subset of properties.
Searchable Properties
name
sku
gtin
metadata._search
To search, simply provide a string to search by using the search
query param.
If you want to highlight matching search results for a frontend, we provide a special property for search-returned shipment objects called _search
which will have the matched text surrounded with <mark>
handles.
Ordering Search Results
By default, search results are ordered by relevance. However, if you include an order_by
parameter along with your search query, the results will be ordered by the specified property instead of by relevance.
Relevance Score
Relevance scores are included in the search results by default. Note that this could add up to 10ms of extra time to the request.
Delete Item
You can delete an item by using its ID. All information about the item will be lost. Any shipments, manifests, or fulfillments that are completed will not be impacted, but the reference to that item ID will be broken.