477 posts tagged with "API"

Webhook event type and timestamp in payload body​

The nautical_event_type and nautical_event_timestamp fields are now part of every webhook payload body, whereas previously this information was only accessible from the header. For example:

  "nautical_event_type": "nautical_order_created",
  "nautical_event_timestamp": "2024-02-22T15:24:19.374608-05:00",

Ledger-based payout system​

Introduced a new ledger-based payout system that provides more accurate financial tracking and reporting. Payouts can now be connected to individual fulfillment lines, enabling more granular commission calculations and financial record-keeping.

Journal entry queries​

Added the ability to query journal entries through the API, providing visibility into financial transaction records for accounting and reconciliation purposes.

Analytics integration for internal testing​

Enabled analytics tracking on emails for internal testing purposes, allowing the team to monitor email performance and engagement.

Enhanced payout validation​

Added validation to prevent multiple draft payouts from being created simultaneously, ensuring data consistency and preventing potential conflicts in the payout workflow.

Fixed several issues to improve system reliability:

• Resolved ledger-related issues discovered during end-to-end testing
• Corrected field definitions for the Ledger API type
• Fixed data mapping issues that could cause inconsistencies
• Resolved fixture file problems affecting development and testing environments

Firebase Authentication plugin​

Added support to connect to Firebase authentication, a tool that supports various sign-in methods, including social logins and email/password combinations. This plugin leverages Firebase's secure user token to authenticate users within Nautical, proving a seamless sign-on experience.

Learn more ->

Available shipping methods API field​

Added the availableShippingStrategy field to the MarketplaceConfiguration model. This field determines how available shipping methods are calculated for price-based shipping rates.

• When SELLER_LINES (default), the calculation of available shipping methods for each seller is based solely on that seller's order total.
• When MARKETPLACE_LINES, the calculation includes the entire marketplace order total for determining available shipping methods for each seller.

Fixed an issue where the vendor_payout_confirmation email was not being sent after processing payouts.

Fixed an issue where you could not filter sellers with the PAUSED status.

Fixed an issue where a customer user could use another customer's order token to access details of that order via the API.

Enhanced payment ledger tracking​

Payments can now be connected to journal entries, providing better tracking of payment transactions in the accounting system. When payments are captured, they are automatically recorded in the ledger, improving financial accuracy and reporting.

Guest customer receivable ledger​

Added support for tracking receivables for guest customers, ensuring accurate financial records even when customers check out without creating an account.

Automated ledger recording for orders​

Order finalization now automatically records transactions to the ledger, including:

• Revenue recognition based on marketplace configuration
• Commission calculations per seller order
• Agreement fees tracking
• Discount accruals
• Manual fee recording

Marketplace operators can now configure when orders accrue revenue (on placement or finalization), giving more control over financial reporting.

Refresh tokens for customer authentication​

The createCustomerToken mutation now returns refresh tokens along with JWT tokens, improving the authentication flow and session management for customers.

Enhanced user type differentiation​

Firebase registration now properly differentiates between buyers, sellers, and staff users, providing better user management and authentication handling.

Explicit shipping strategy configuration​

Marketplace operators can now explicitly configure the shipping calculation strategy (net vs. gross pricing) in marketplace settings, providing more control over how shipping costs are calculated and displayed.

Performance improvements​

Made several performance improvements across the platform:

• Commission calculations are now optimized for partial quantities
• Ledger insertions are now batched, reducing database overhead
• Journal entry creation during order placement is more efficient

Fixed issues with payout confirmation emails that could fail to send in certain scenarios.

Fixed an issue where filtering for paused sellers was not working correctly.

Fixed an issue where API requests on non-API routes could fail if the app context was not properly initialized.

Fixed permissions so that orders are now only accessible to users with manager-orders permissions, improving security and data access control.

Fixed calculation issues with available shipping methods to use gross totals instead of net totals, ensuring accurate shipping cost calculations.

Fixed an issue where sale discounts were not being included in ledger transactions.

Deprecated the payout.penalties field in favor of negative adjustments. This field is scheduled for removal after July 1, 2024.

Firebase plugin OAuth support​

Added OAuth authentication support for the Firebase plugin, enabling more secure integration options.

Ledger system foundation​

Introduced a new ledger system for tracking financial transactions across the marketplace. This includes:

• Automatic ledger creation for all sellers and buyers
• Feature flags to control ledger functionality rollout
• Enhanced payout tracking capabilities

This foundational work will enable more detailed financial reporting and transaction tracking in future releases.

Document upload size increase​

Increased the maximum allowed document upload size from 5 MB to 15 MB, making it easier to upload larger product documentation and images.

Default variant management improvements​

Product creation and updates now handle default variants more flexibly in certain edge cases, improving the product management experience.

Fixed an issue where vendor payout fees were using an incorrect field name, which could cause payout calculations to fail.

Resolved an issue affecting affiliate order handling when gross amounts and taxes were removed from calculations.

Fixed migration dependency issues that could prevent fresh installations from completing successfully.

Generate refund receipts​

Added the ability to generate refund receipts with the invoiceRequest mutation. You must provide the refundId as an argument, for example:

mutation {
  invoiceRequest(refundId: "UmVmdW5kOjUzOA==") {
    invoice {
      id
      url
    }
  }
}

PayPal payout plugin​

Added the nautical.payments.paypal plugin for using PayPal as the payout gateway.

Trolley payout plugin​

Added the nautical.payments.trolley plugin for using Trolley as the payout gateway.

Webhook queue manager logging improvements​

Improved the logging of webhook events for queue management plugins, such as Google PubSub. Whereas previously logs were only created for failed transmissions, we now also capture and log successful webhook events.

Seller order number in webhooks​

Order webhooks now include the number field, which is populated with the seller order number.

Fixed an issue where voucher discounts requiring a minimum order value were applied based on the gross total, including tax, rather than the net order total.

PayPal payout support​

Added the ability to process seller payouts through PayPal, including customizable payout email configuration and seller-level PayPal plugin enablement.

Trolley payout integration​

Introduced support for processing payouts via Trolley (formerly TransferWise), enabling automated recipient creation and batch payout processing.

Refund receipts​

Added automatic generation of refund receipt PDFs when refunds are paid, with customizable templates and support for both manual and automatic receipt creation through the invoiceRequest mutation.

Simplified product type management​

Product types no longer require the hasVariants field or simple/configurable distinction. Products can now be created with more flexibility in how variants are managed, controlled via marketplace configuration settings.

Payment gateway filtering​

Added the ability to filter available plugins to specific payment gateways, providing more control over which payment methods are available in different contexts.

Payout gateway tracking​

The VendorPayout model now stores which payment gateway was used for each payout, improving traceability and reporting.

Fixed an issue where shipping costs were not properly calculating taxes in certain scenarios.

Fixed an issue where users could refund more than the total shipping cost across multiple refunds for the same order.

Fixed an issue that prevented order line refunds after manual refunds were cancelled, by properly filtering out cancelled refunds during validation.

Fixed voucher minimum amount validation to use net total instead of gross total, ensuring discounts are applied correctly.

Fixed an issue in the Shopify integration where the order_updated webhook was not specifying the correct order ID.

Added the missing number field to order webhook payloads, ensuring complete order data is sent to webhook subscribers.

Fixed an issue where draft order CSV exports could fail in certain scenarios.

Fixed an issue where inactive plugins could still affect order calculations and processing. Plugins now only execute when actively enabled.

Order line refunds API​

Refund lines can now be scoped to an OrderLine, allowing you to target refunds to specific individual order lines. To achieve this, use the refundLinesAdd mutation and set the refundScope to the id of the desired order line. Additionally, specify the quantity of the order line that should be included in the refund.

Learn more ->

Draft order lines CSV upload API fields​

Added the following mutations for uploading a CSV file to create draft order lines:

• nauticalOrderLinesCsvUpload
• orderLinesCsvUpload

The CSV file must have at least three columns: id_type, id, and quantity. See the following sample format:

id_type, id, quantity
NSN, 5669abb7-8c4f-477f-8662-4540af3bcdac, 5
ID, UHJvZHVjdFZhcmlhbnQ6MjEx, 5
SKU, 998323573, 5
ID, UHJvZHVjdFZhcmlhbnQ6MjEz, 5

Test taxes plugin​

Added a "Nautical Test Taxes" plugin, which can be used for development and testing with taxes.

Within the plugin settings, you can input a single tax percentage, which should fall within the range of 0 to 100%. This plugin respects tax settings such as "Charge taxes on shipping rates" and "All products prices are entered with tax included."

Tax changes on manual fixed-amount refunds​

When processing a manual refund for a fixed amount, taxes are no longer added separately. The fixed amount entered is the after-tax amount.

Fixed amount refunds do not automatically adjust records in the tax engine, such as Avalara. If you need to modify the amount of tax to remit, you must manually create a tax adjustment within Avalara.

CSV upload for order lines​

Added the ability to upload order lines via CSV, making it easier to bulk import order data into the platform.

Dashboard embedding tokens​

Introduced a new DashboardEmbeddingToken mutation that enables secure embedding of analytics dashboards, with support for seller-specific data filtering.

PayPal payout gateway​

Added initial support for PayPal as a payout gateway, providing more options for marketplace operators to distribute seller payouts.

Simplified fixed amount refunds​

Fixed amount refunds no longer include tax calculations, streamlining the refund process for operators.

WorkOS authentication improvements​

Enhanced WorkOS integration with strongly typed plugin configuration and support for specifying authentication providers in authorization URLs.

Fixed an issue where the default refund type was not properly set to order line refunds.

Fixed a bug preventing storefront order shipping cost refunds from processing correctly.

Fixed an issue where order line refunds were incorrectly allowed after manual refunds had been processed.

Fixed a bug where shipping prices were not properly set to zero when orders were cancelled after being declined.

Fixed validation issues in refund calculations to ensure accurate refund amounts based on order line quantities and amounts.

Fixed an issue where previously refunded order line quantities were not correctly accounted for in subsequent refund requests.

Fixed an issue with Avalara tax integration where zero-tax return invoices were not being posted correctly due to missing entity use codes.

Resolved several issues with Stripe card payment processing affecting initial card transactions.