Traide Documentation

Custom fields allow you to add extra structured data to specific marketplace objects. Data validation is based on the input type assigned to the attribute. Custom fields can be applied to the following objects:

• User (includes Customers and StaffMembers)
• Product
• Variant
• Category
• Collection

Custom fields can be managed via repeatable templates (which apply to every instance of an object model) or by directly assigning attributes to individual instances (if the marketplace configuration allows).

The Shopify integration allows for the following data flows and management capabilities:

• Product Listing: Import Shopify products directly into the marketplace.
• Pricing: Optional price synchronization to keep Shopify and Traide prices aligned, or maintain separate pricing strategies.
• Inventory: Shopify acts as the source of truth for inventory and product information.
• Order Management: Sellers can use Shopify as their primary Order Management System (OMS). Order cancellations and fulfillments in Shopify are synchronized back to Traide.
• Taxonomy: Product templates and attributes are created automatically from Shopify data, which may not be standardized across different sellers.

Draft orders allow marketplace operators to create orders on the backend without requiring the buyer to perform a checkout on the storefront. This is useful for phone orders or custom quotes. Key characteristics include:

• Ability to override shipping costs and product prices.
• Potential to update inventory levels (marking products as allocated) based on marketplace stock allocation settings.
• Requirement for a registered customer account (guest checkout is not supported for draft orders).

Marketplace operators can issue partial or full refunds to a buyer's original payment method. Refunds can be scoped to the entire marketplace order, specific seller orders, or individual line items.

Key constraints:

• Permissions: Staff must have the Manage refunds permission assigned to their permission group.
• Payment Methods: All refunds for a single order must use the same payment method.
• Consistency: Once a refund method (Order line or Manual) is used for an order, subsequent refunds for that same order must use the same method; mixing methods is not allowed.
• Currency: Refunded amounts are returned in the original transaction currency.

Stripe Tax is a tax engine integrated into Traide that automatically calculates tax rates at checkout and records tax transactions against orders. It specifically handles the complexity of marketplace taxes where a single basket may contain multiple sellers with different tax footings. Key capabilities include:

• Checkout: Live rate calculations for line totals, basket subtotals, and order totals.
• Per-seller shipping tax: Apportions marketplace-level and seller-level shipping across sellers and taxes them based on each seller's specific footing.
• Order Transactions: Records real Stripe tax transactions for accurate reporting.
• Refunds and Declined Fulfillments: Automatically reverses corresponding taxes when a line is refunded or a fulfillment is declined.

The standard Stripe payment process in Traide follows these sequential steps:

1. Initiate Payment: Traide requests a Stripe payment intent for the order total using the getClientSecret query.
2. Generate Form: The returned payment intent secret key is used to render the secure Stripe payment form on the client side.
3. Capture Method: The buyer enters payment details (e.g., credit card) and confirms the transaction.
4. Finalize Order: Once confirmed on the client, the backend sequence is:
   • Stripe attaches the payment method to the payment intent.
   • Traide creates a payment record using the checkoutPaymentCreate mutation and the payment intent token.
   • Traide completes the checkout and creates the order using the checkoutComplete mutation.
5. Processing: The payment is authorized or captured based on the configured Stripe payment capture mode.

Shipping rates define the costs to ship orders from a specific shipping zone based on order size. There are two primary calculation methods:

1. Price-based: Calculates costs based on product prices. The total used (seller order total vs. marketplace order total) depends on the 'Shipping options calculated by' setting in the fulfillment model.
2. Weight-based: Calculates costs based on the total weight of the products in the order.