: Staging
: Production
🪲 Fixed
Fixed a critical database issue that was affecting platform stability. This release restores normal operation.
: Staging
: Production
Fixed a critical database issue that was affecting platform stability. This release restores normal operation.
Added an advancedSearch filter to search by specific fields for a faster, more targeted search, as opposed to the pre-existing search filter, which searches across all fields.
You can use the advancedSearch argument in the ProductFilterInput for advanced filtering by search term when querying products and variants.
The fields you can target for search are defined in the ProductSearchFieldEnum and ProductVariantSearchFieldEnum. If you don't define search fields, the filter defaults to search only by NAME.
query {
products(
first: 25
filter: {
advancedSearch: {
searchTerm: "shiny"
searchFields: [
NAME,
VARIANT_NAME,
DESCRIPTION,
CATEGORY_NAME]
}
}
) {
edges {
node {
id
name
description
}
}
}
}
Added the ability to retrieve the list of Avalara tax exempt codes through a new taxExemptCodes query.
query {
taxExemptCodes {
code
name
validCountries
}
}
Added the dimension argument to filter by time period for the following marketplace insight queries:
insightsOrdersMarketplaceSummaryinsightsMarketplacePaymentsSummaryinsightsMarketplaceTaxSummaryThe values for the dimension argument are defined by the InsightDimensionEnum.
startDate and endDate are now required for all insights queries.perspective filter argument input type changed from string to PerformancePerspective. insightsTopPerformingCategoriesinsightsTopPerformingProductsdimension argument changed from string to InsightDimensionEnum. This must be updated in any logic using insightsOrdersMarketplaceSummary queries.ColumnObjectType, FilterObjectType, and other fields depending on the report type. For example, InReportMarketplaceAffiliatePayoutsSummaryType now requires category, title, summary, and report.GraphDataType object, the period field was renamed to dimension.Added the ability to set product availability while creating products through the API. The productCreate mutation input now supports the isAvailable and startDate fields.
mutation {
productCreate(
input: {
isAvailable: true
productType: "UHJvZHVjdFR5cGU6NDM5"
name: "Snow Pants"
seller: "U2VsbGVyOjI="
basePrice: "50"
}
)
{
product {
name
isAvailable
}
}
}
mutation {
productCreate(
input: {
startDate: "2023-03-24"
productType: "UHJvZHVjdFR5cGU6NDM5"
name: "Snow Pants"
seller: "U2VsbGVyOjI="
basePrice: "50"
}
)
{
product {
name
startDate
}
}
}
Added the ability for users with the Manage marketplace permission to force order fulfillment for a line with a deleted variant, by passing the allowNullVariants field with the orderFulfill mutation input.
mutation {
orderFulfill(
order: "T3JkZXI6MQ==",
input: {
lines: [
{
orderLineId: "ABC=",
stocks: [
{
quantity: 1,
warehouse: "ABC=="
}
]
}
],
notifyCustomer: false,
allowNullVariants: true
}
) {
orderErrors {
field
message
code
warehouse
orderLine
variant
}
order {
id
number
}
fulfillments {
id
fulfillmentOrder
status
}
}
}
Added the ability to set the seller status while adding a new seller with the sellerDataCreate mutation.
A new status field is added to SellerInput. The status field accepts values from the SellerStatusEnum. If unspecified, the status defaults to PENDING.
mutation {
sellerDataCreate(
input: {
name: "Cosmic Shirts Co"
owner: "VXNlcjo3NDM4"
plan: "QWdyZWtZW50Ojc="
status: APPROVED
}
){
ok
seller {
id
companyName
status
}
}
}
Added the availablePayoutBalance read-only field to the order object, to return the balance remaining to be paid out.
query {
order(
id: "T3JkZXI6MTIyMTY="
)
{
id
availablePayoutBalance {
amount
currency
}
}
}
Added the ability to filter the orders query by payoutStatus, which accepts values from the OrderPayoutStatusEnum.
query {
orders(
first: 10
filter: {
payoutStatus: READY_FOR_PAYOUT
}
)
{
totalCount
edges {
node {
id
availablePayoutBalance {
amount
}
}
}
}
}
Added the orderOfferConvertToNauticalQuoteOrder mutation to convert an offer order to a Nautical (marketplace) quote order. You can target the id of either an order or Nautical order.
mutation {
orderOfferConvertToNauticalQuoteOrder
(id: "VXNlcjo3MtYw")
{
order {
id
status
created
}
orderErrors {
field
code
message
}
}
}
Added the ability for a customer to add and manage public metadata to their own checkout(s) through the API, for example using the metadataUpdate mutation on checkout.
This functionality must be turned on in your environment before it can be used. Contact a Nautical support representative to enable this functionality in your marketplace.
Added the vatIdentificationNumber field to the user object, for example to store and display a customer's VAT identification number on an invoice.
query {
user(
id:"VXNlcjo3MjYw"
)
{
vatIdentificationNumber
}
}
Added the ability to assign Avalara tax exempt codes to users, through a new Tax Exempt Code field on the customer object.
Through the API, you can assign tax codes by passing the taxExemptCode field through the customerUpdate mutation.
mutation {
customerUpdate(
id: "VXNlcjo3MjI2"
input: {
taxExemptCode: "R"
}
)
{
user {
id
taxExemptCode
}
}
}
Updated the sellerDataUpdate mutation response to show error messages, by adding the ability to return sellerErrors in addition to the existing ok boolean success indicator.
.csv or .xlsx file when one or more fields were selected for export.products and productVariants query.This release also includes changes from the 1.3.1 hotfix.
tax_exempt_code field for a customer.This release was patched to a designated environment. Other customers will receive these changes with the 1.3.2 release.
tax_exempt_code field to the user object, along with associated queries and mutations.updateSellerData mutations to fail.calculate_order_line_unit for the Avatax plugin, which was preventing seller admins from adding products to quotes.This release also includes changes from the 1.2.22 hotfix.
shippingMethodPriceOverrideAmount field with the checkoutSellerShippingMethodsUpdate mutation.productVariants query by the seller global ID.date and filter by from_email, to_emails, message_type, and date for the emailLogs query.marketplace_order field to the order object model, for the ability to retrieve the marketplace order from the seller order.SELLER_CREATEDSELLER_UPDATEDSELLER_AGREEMENT_ACKNOWLEDGEDwishlistItem. Users of the legacy wishlist model, which stores multiple variants, must update their implementation to the new model as it is no longer possible to associate multiple variants with a wishlistItem. This update provides more flexibility in wishlist management.attributes query for improved speed and performance.shop query.context_key name in WishlistByIdLoader.This release was patched to a designated environment. Other customers will receive these changes with the 1.2.24 release.
externalPayoutStatus could not be determinedThis release also includes changes from the 1.2.20 hotfix.
DraftOrder mutations.overrideAmount in draftOrderLinePriceOverride and nauticalDraftOrderLinePriceOverride mutations to ensure the input is not negative or zero.line_price_overridden error that occurred during order events after using draftOrderLinePriceOverride or nauticalDraftOrderLinePriceOverride mutations to override item price in draft orders.This release was patched to a designated environment. Other customers will receive these changes with the 1.2.21 release.
wishlistAddProduct and wishlistAddProduct mutations to support specifying the target user with user_idSELLER_CREATION) form