439 posts tagged with "API"

Visibility field for collections​

Added the isVisible boolean field to the collection object.

New seller statuses​

Added the following statuses to the SellerStatus enum:

• SUSPENDED
• BANNED
• DEACTIVATED

Customer order count​

Changed customer.numOrders to resolve the total number of marketplace orders instead of seller orders.

Fixed an issue preventing the order refund confirmation and CSV export emails from sending.

Fixed an issue with Stripe webhook processing to handle webhook errors appropriately.

Payout ledger integration​

Payouts are now tracked through the ledger system, providing improved accuracy and transparency. Payout data is now connected to orders, enabling better financial reporting and reconciliation.

Payout fee visibility​

Fees associated with vendor payouts are now exposed in the payout summary, giving sellers clearer insight into their earnings.

Order payout status tracking​

Orders now include a payoutStatus field that reflects the current payout state based on ledger data, making it easier to track which orders have been paid out to sellers.

Available payout balance​

Added availablePayoutBalance to orders, showing the amount that can be paid out to sellers at any given time.

Seller commission tracking​

Orders now include a sellerCommission field that calculates commission amounts directly from ledger data.

Additional seller status options​

Added new seller status options including "Suspended," "Banned," and "Deactivated" to provide more granular control over seller accounts.

Product type cascading deletion​

When deleting a product type where require_product_types is enabled, all associated variants and products are now automatically removed, simplifying product type management.

Collection visibility control​

Collections now include an isVisible field, allowing marketplace operators to control which collections are displayed to customers.

Order fulfillment and cancellation improvements​

Made several improvements to order handling:

• Fulfillment cancellations now update ledgers appropriately to maintain accurate financial records.
• Order cancellations are properly recorded in the ledger system.
• Declining fulfillments now correctly updates ledger entries.
• The system now accurately determines when a seller's portion of an order is completely fulfilled.

Fixed an issue where the nauticalOrderByToken query could allow sellers to access orders that didn't belong to them.

Fixed an issue where digital fulfillment revenue wasn't being accrued correctly in the ledger system.

Fixed an issue where the customer.numOrders field was counting individual seller orders instead of marketplace-level orders.

Fixed an issue with SendGrid email payloads that could cause emails to fail when data wasn't in the correct format.

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.