Summary

This mapping documentation describes how Shopware deposit (Ticket) transactions are transferred to iPaaS.com, together with the deposit's address, payment, and line items. A deposit is a Shopware deposit/Ticket transaction whose order number ends in "-D"; it represents the deposit portion of an order rather than a standard order. The parent Add Shopware Order Deposit TO iPaaS.com collection dispatches the deposit to iPaaS.com as a Transaction of type Ticket and links it back to its parent order, while the child collections move the deposit's address, payment, and line items as part of the same transfer.

ID Format

Manual Sync ID Format

The parent collection's mapping filter returns false, so deposits are not transferred by entering an ID on the iPaaS.com Manual Sync page or by subscribing to a Shopware order event. Deposit (Ticket) transactions reach this collection only through the integration's deposit flow, which routes a deposit to the parent collection when the deposit is created. The child address, payment, and line item collections have no independent trigger and run only as part of a parent deposit transfer. If a subscriber inspects a deposit ID, it is the parent order ID with a "-D" suffix appended, for example 01915630e5db7214ab1ab2dc71608955-D.

External ID Format

After a deposit is transferred, it is filed in iPaaS.com as a Transaction of type Ticket and identified by its TransactionNumber, which carries the Shopware order number for the deposit (the value ending in "-D"). The deposit is linked to its parent order in iPaaS.com by stripping the "-D" suffix from the deposit ID to recover the parent order ID and resolving the matching iPaaS.com Transaction. The child address, payment, and line items stay associated with the deposit transaction created by the parent transfer.

Deleted Record Support

This family transfers deposit creates only — the parent and all three child collections are Add-only. There is no deposit delete collection in this family, so deposit, address, payment, or line item deletions in Shopware are not propagated to iPaaS.com by default. Removing a deposit or any of its sub-records from iPaaS.com when it is deleted in Shopware must be handled separately.

Custom Field Support

The parent collection stores two Shopware-specific values on iPaaS.com Transaction custom fields: Shopware Currency Name (the deposit's currency, resolved from the Shopware currency ID to a readable name) and Shopware Sales Channel (the Shopware sales channel ID the deposit was placed through). Both are populated by mappings in the parent collection — the currency name through a Dynamic Formula that resolves the Shopware currency ID, and the sales channel through a direct field mapping. The exact formulas appear in the Mappings section below.

Mapping Collection Status

Add Shopware Order Deposit TO iPaaS.com (parent): Disabled. The collection is present in the integration, but its mapping filter returns false, so it does not process records through the standard order webhook or Manual Sync path. Deposits reach it only through the integration's deposit flow.
Add Shopware Order Deposit Address TO iPaaS.com (child): Enabled
Add Shopware Order Deposit Payment TO iPaaS.com (child): Enabled
Add Shopware Order Deposit Line Item TO iPaaS.com (child): Enabled

Trigger Events

The parent collection has no Shopware order webhook subscription and no Manual Sync trigger for deposits. Its filter returns false; deposit (Ticket) transactions are added through the integration's deposit flow, which routes a deposit to the collection when the deposit is created.
The child address, payment, and line item collections have no independent trigger. They run automatically whenever the parent deposit transfer runs.

Duplicate or Conflicting Mappings

This family transfers deposits from Shopware to iPaaS.com as Transaction records, together with their addresses, payments, and line items. The standard order collection, Add/Update Shopware Order TO iPaaS.com, transfers non-deposit orders and explicitly excludes deposits (order numbers ending in "-D"), so the two do not transfer the same record. Opposite-direction collections that write Transaction, Transaction Line, or Transaction Payment data back into Shopware may also be configured in the integration; order and address data flowing from iPaaS.com into Shopware is handled through the order inbound flow rather than standalone deposit collections.

Before enabling any inbound "From iPaaS.com" Transaction, line item, or payment collection alongside these outbound collections, subscribers or their MiSP should review and customize the mapping collection filters to prevent circular updates, and define clearly which system is the source of truth for transaction data.

Unmapped Field Overwrite Risk

The parent and payment collections are Add-only, so the full-record-replace behavior that applies to Update transfers does not arise on the deposit transaction itself. On the parent collection the only standard Transaction fields not mapped are Id and TransactionUpdatedDateTime, both managed by iPaaS.com (a server-assigned identifier and a server-set timestamp). On the payment collection the standard MethodInfo field is not mapped; because the collection only adds records, no existing value is overwritten on transfer, and subscribers who want to populate MethodInfo can add a mapping for it.

The address and line item child collections are also Add-only, but the iPaaS.com API performs a full record replace when updating those record types. If either collection is later paired with an Update collection, any existing value in the following unmapped standard fields is overwritten with an empty value on each Update transfer, unless a mapping is added to preserve it:

Add Shopware Order Deposit Address TO iPaaS.com: ShipDate, ShippingAmount, ShippingMethodDescription.
Add Shopware Order Deposit Line Item TO iPaaS.com: DiscountAmount, DiscountPercent, EstimatedTaxAmount, QtyShipped, Weight.

To preserve such values, keep the Add collection paired with a separate Update collection and, in the Update collection, add a Dynamic Formula mapping that uses the DestinationValue function to carry the existing iPaaS.com value forward — for example, DestinationValue.Weight mapped to the iPaaS.com Weight field. The DestinationValue function reads the current value from the iPaaS.com destination record before the replace and writes it back into the outgoing record, so the value is preserved.

Supported Child Collections

Add Shopware Order Deposit Address TO iPaaS.com (Transaction Address): Transfers the deposit's addresses as part of the deposit transfer. Each address carries resolved Country and Region names and is flagged IsPrimaryBilling or IsPrimaryShipping when it is the deposit's billing or shipping address. Addresses stay associated with the deposit transaction created by the parent transfer.
Add Shopware Order Deposit Payment TO iPaaS.com (Transaction Payment): Transfers the deposit's payment as part of the deposit transfer, with the payment method name, description, status, and amount resolved from Shopware.
Add Shopware Order Deposit Line Item TO iPaaS.com (Transaction Line): Transfers the deposit's qualifying line items as part of the deposit transfer, with the SKU, status, tax percent, and discount-distributed extended price resolved per line.

Shopware Caveats

Deposit order numbers end in "-D": A deposit is identified by the "-D" suffix on its Shopware order number. The deposit is linked to its parent order by removing that suffix to recover the parent order's ID.
Order state names are language-dependent: Shopware returns the order state name in the store's configured language, so the Status translation matches the English spellings of each state. Stores configured in another language may need the status mapping extended so their state names map to the correct iPaaS.com status; otherwise those deposits default to Pending. This applies at the time this documentation was written.
Country and Region resolution: On the address collection, the Country and Region names are resolved from Shopware's country and country-state IDs and depend on those IDs existing in Shopware. If an ID cannot be resolved, the corresponding name is left empty.
Shipping method and shipping flag depend on tracking: On the address collection, the ShippingMethod name and the IsPrimaryShipping flag are derived from the parent deposit order's tracking information. If the parent deposit has no tracking record, the shipping method name is empty and the shipping flag is false for every address on the order.
Payment method resolution: On the payment collection, the Method and Description values are resolved by looking up the Shopware payment method by its ID. If the ID is empty or the method cannot be found, both fields are left empty. The Status value depends on the Shopware transaction state ID resolving to a state name; if it cannot be resolved, the status is empty.
Tax and discount on line items: On the line item collection, TaxPercent is the sum of the line's tax rates; a line with no tax rules transfers with a tax percent of 0. The ExtendedPrice depends on the parent deposit's promotions to compute each line's share of the header-level discount; if the deposit has no promotions, no discount is distributed and the extended price equals the line total.

iPaaS.com Caveats

Customer, company, and parent order must be linked first: A deposit is linked to its customer or company in iPaaS.com by an existing cross-platform link, and to its parent order by the parent order's iPaaS.com Transaction link. If the customer, company, or parent order has not yet been linked, the related record must be transferred first so the link can be established before the deposit is filed.
Child collections run only with their parent: The address, payment, and line item collections run only as part of a parent deposit transfer. They cannot be triggered independently from the Manual Sync page; transfer the parent deposit to move its sub-records.
API throttling on large jobs: The subscription exposes configurable API throttle limits. Subscribers should stagger large manual jobs and rely on the configured throttle limits when transferring many deposits at once.

Integration-Specific Caveats

Collection disabled by default: The parent collection is intentionally disabled by default through its return false filter. Subscribers who use deposit/ticket orders must enable the deposit flow for their implementation; until then, no deposit is transferred by this collection. This applies at the time this documentation was written.

Setup Requirements

Deposits are not transferred by subscribing to a Shopware order event or by entering an ID on the Manual Sync page. The parent collection's mapping filter returns false, and deposits reach the collection only through the integration's deposit flow. Subscribers or their MiSP who use deposit/ticket orders should work with their MiSP to enable the deposit flow for their implementation; no Inbound Data Flows (External Webhooks) subscription drives this collection directly.

Because the deposit is linked to its parent order, customer, and company by existing cross-platform links, those related records must already be transferred and linked in iPaaS.com before a deposit is transferred.

Integration Flow

The integration's deposit flow routes a deposit (Ticket) transaction to the parent Add Shopware Order Deposit TO iPaaS.com collection when the deposit is created. The collection's filter returns false on the standard order webhook and Manual Sync paths, so no standard order event drives it.
The integration retrieves the deposit record from Shopware, including its addresses, payment, and line items.
The deposit's core values are transformed: the transaction type is set to the static value Ticket, the order state is translated into an iPaaS.com status, promotions are summed into a discount amount, line quantities are summed into a total quantity, and the Shopware currency is resolved to a readable name stored as a custom field.
The deposit is linked to the correct iPaaS.com customer (or, for business orders, the correct iPaaS.com company) and connected system, and to its parent order by stripping the "-D" suffix to recover the parent order ID and resolving the matching iPaaS.com Transaction.
The deposit is written to iPaaS.com as a Transaction of type Ticket, identified by its TransactionNumber.
Each of the deposit's addresses is processed through the child Add Shopware Order Deposit Address TO iPaaS.com collection; the deposit's payment through the child Add Shopware Order Deposit Payment TO iPaaS.com collection; and each qualifying line item through the child Add Shopware Order Deposit Line Item TO iPaaS.com collection. Promotion line items are excluded from the line transfer.
The deposit transaction is linked in iPaaS.com so the address, payment, and line items stay associated with it.

Mappings

Add Shopware Order Deposit TO iPaaS.com

Mapping Filter

return false;

Filter Description. The filter return false causes the collection to skip every record presented to it on the standard order webhook and Manual Sync paths — no Shopware order event causes a record to flow through this collection, and no record is matched by a filter expression on incoming order records. The collection is intentionally disabled by default; deposit (Ticket) transactions are added only through the integration's deposit flow, which routes a deposit to the collection when the deposit is created. The filter does not throw an exception; records simply do not pass. Subscribers who use deposit/ticket orders must enable the deposit flow for their implementation.

Description: Transfers the deposit (Ticket) transaction's core commercial values from Shopware to iPaaS.com as a Transaction of type Ticket, linking it to its customer or company, connected system, and parent order.

Mapping Type	Source Field (Shopware)	Destination Field (iPaaS.com)	Description
Static	`"Ticket"`	Type	recommended — Sets the iPaaS.com Transaction type to the static value Ticket so the record is filed as a deposit rather than a standard order.
Field	OrderNumber	TransactionNumber	recommended — Maps the Shopware order number for the deposit (ending in "-D") to the iPaaS.com Transaction number, the primary human-readable identifier used to find and reconcile the deposit.
Field	PositionPrice	Subtotal	recommended — Maps the Shopware order position price (line-item prices before shipping and tax) to the iPaaS.com Transaction subtotal.
Field	AmountTotal	Total	recommended — Maps the Shopware order amount total to the iPaaS.com Transaction total so the deposit's grand total reconciles.
Dynamic Formula	`Price_CalculatedTaxes`	TaxAmount	recommended — Maps the deposit's calculated product taxes to the iPaaS.com Transaction tax amount. The disabled trailing term can be enabled to also include shipping taxes.
Field	ShippingTotal	ShippingAmount	recommended — Maps the Shopware order shipping total to the iPaaS.com Transaction shipping amount.
Field	Email	EmailAddress	recommended — Maps the ordering customer's email address to the iPaaS.com Transaction email address for identifying the customer on the deposit.
Dynamic Formula	`SpaceportSystemId`	SystemId	recommended — Supplies the iPaaS.com system identifier so the deposit is filed under the correct connected Shopware system. Resolved automatically at transfer time; leave in place.
Dynamic Formula	Resolve customer (see formula below)	CustomerId	recommended — Resolves the iPaaS.com customer identifier with GetSpaceportIdAsync so the deposit is attached to the correct customer; empty when no link exists.
Dynamic Formula	Resolve company (see formula below)	CompanyId	recommended — Resolves the iPaaS.com company identifier with GetSpaceportIdAsync for B2B deposits; empty when the customer is an individual.
Dynamic Formula	Resolve parent order (see formula below)	ParentId	recommended — Strips the "-D" suffix to recover the parent order ID and resolves the matching iPaaS.com Transaction with GetSpaceportIdAsync so the deposit is associated with its parent order; empty when the parent order is not yet linked.
Dynamic Formula	Translate order state (see formula below)	Status	recommended — Translates the Shopware order state into an iPaaS.com status using TransactionStateNameFromId: Done becomes Complete, Cancelled/Order clearance denied become Cancelled, all others default to Pending.
Dynamic Formula	`GetQtyOfLines(Transaction_Line)`	TotalQty	recommended — Sums the quantities of all line items with GetQtyOfLines; returns 0 when the deposit has no line items.
Dynamic Formula	`return await GetSumOfPromotions(Promotions);`	DiscountAmount	recommended — Sums the value of every promotion on the deposit with GetSumOfPromotions; returns 0 when there are no promotions.
Dynamic Formula	`DateTimeOffsetFromLocalDateTime(OrderDateTime)`	TransactionCreatedDateTime	recommended — Sets the iPaaS.com Transaction creation date-time from the Shopware order date using DateTimeOffsetFromLocalDateTime; empty dates follow the iPaaS.com default.
Dynamic Formula	Resolve currency name (see formula below)	Shopware Currency Name	optional — Resolves the Shopware currency ID to a readable name with GetCurrencyNameById and stores it on an iPaaS.com custom field; empty when no matching currency is found.
Field	SalesChannelId	Shopware Sales Channel	optional — Stores the Shopware sales channel ID the deposit was placed through on an iPaaS.com custom field for sales-channel-specific handling.

// TaxAmount
Price_CalculatedTaxes // + ShippingCosts_CalculatedTaxes

// CustomerId
return await GetSpaceportIdAsync(CustomerId, "Customer", SpaceportSystemId);

// CompanyId
return await GetSpaceportIdAsync(CustomerId, "Company", SpaceportSystemId);

// ParentId
return await GetSpaceportIdAsync(Id.Substring(0, Id.Length - 2), "Transaction", SpaceportSystemId);

// Status
var status = await TransactionStateNameFromId(StateId);
switch(status)
{
  case "Cancelled":
  case "Order clearance denied":
    return "Cancelled";
    break;
  case "Done":
    return"Complete";
    break;
  default:
    return "Pending";
    break;
}

// Shopware Currency Name
return await GetCurrencyNameById(CurrencyId);

Add Shopware Order Deposit Address TO iPaaS.com

Description: Child collection that transfers each of the deposit's addresses to iPaaS.com as a Transaction Address, including resolved Country and Region names and billing/shipping flags.

Mapping Type	Source Field (Shopware)	Destination Field (iPaaS.com)	Description
Field	FirstName	FirstName	optional — Maps the recipient first name on the Shopware deposit address to the iPaaS.com Transaction Address first name.
Field	LastName	LastName	optional — Maps the recipient last name on the Shopware deposit address to the iPaaS.com Transaction Address last name.
Field	Company	Company	optional — Maps the company name on the Shopware deposit address to the iPaaS.com Transaction Address company, typically for business addresses.
Field	Street	Address1	recommended — Maps the Shopware street to the iPaaS.com Transaction Address first street line for deliverable addresses.
Field	AdditionalAddressLine1	Address2	optional — Maps the Shopware additional address line 1 to the iPaaS.com Transaction Address second street line.
Field	AdditionalAddressLine2	Address3	optional — Maps the Shopware additional address line 2 to the iPaaS.com Transaction Address third street line.
Field	City	City	recommended — Maps the Shopware city to the iPaaS.com Transaction Address city for deliverable addresses.
Field	Zipcode	PostalCode	recommended — Maps the Shopware zip code to the iPaaS.com Transaction Address postal code for deliverable addresses.
Dynamic Formula	`return await CountryNameFromId(CountryId);`	Country	recommended — Resolves the country name from the Shopware Country ID using CountryNameFromId; empty when the ID is invalid or not found.
Dynamic Formula	`return await StateNameFromId(CountryId,CountryStateId);`	Region	optional — Resolves the state/region name from the Shopware Country ID and Country State ID using StateNameFromId; empty when either ID cannot be resolved.
Dynamic Formula	Flag billing address (see formula below)	IsPrimaryBilling	optional — Returns true when this address matches the billing address ID carried on the parent order, false otherwise.
Dynamic Formula	Flag shipping address (see formula below)	IsPrimaryShipping	optional — Returns true when this address matches the shipping address ID on the parent order's first tracking record; false when there is no tracking.
Dynamic Formula	Resolve shipping method (see formula below)	ShippingMethod	optional — Resolves the shipping method name for the shipping address from the parent order's tracking record using GetShippingMethodNameById; empty for non-shipping addresses or when there is no tracking.

// IsPrimaryBilling
if (Id.StartsWith(Parent.BillingAddressId)){return true;}
return false;

// IsPrimaryShipping
if (Parent.Transaction_Tracking != null && Parent.Transaction_Tracking.Count > 0){
  var shippingAddressId = Parent.Transaction_Tracking[0].ShippingOrderAddressId;
  if (Id.StartsWith(shippingAddressId)){return true;}
}
return false;

// ShippingMethod
if (Parent.Transaction_Tracking != null && Parent.Transaction_Tracking.Count > 0){
  var shippingAddressId = Parent.Transaction_Tracking[0].ShippingOrderAddressId;
  if (Id.StartsWith(shippingAddressId)){
    var methodId = Parent.Transaction_Tracking[0].ShippingMethodId;
    return await GetShippingMethodNameById(methodId);
  }
}
return null;

Add Shopware Order Deposit Payment TO iPaaS.com

Description: Child collection that transfers the deposit's payment to iPaaS.com as a Transaction Payment, with the payment method, description, status, and amount resolved from Shopware.

Mapping Type	Source Field (Shopware)	Destination Field (iPaaS.com)	Description
Dynamic Formula	`return await GetPaymentMethodNameById(PaymentMethodId);`	Method	optional — Resolves the Shopware payment method name from its ID using GetPaymentMethodNameById; empty when the ID is empty or the method cannot be found.
Dynamic Formula	`return await GetPaymentMethodNameById(PaymentMethodId);`	Description	optional — Sets the payment description to the same resolved payment method name as Method using GetPaymentMethodNameById; empty when the method cannot be found.
Dynamic Formula	`return await TransactionStateNameFromId(StateId);`	Status	optional — Resolves the payment status from the Shopware transaction state with TransactionStateNameFromId; empty when the state cannot be resolved.
Field	Amount_TotalPrice	Amount	optional — Maps the Shopware payment total price to the iPaaS.com Transaction Payment amount.

Add Shopware Order Deposit Line Item TO iPaaS.com

Mapping Filter

Type!=null && Type!="promotion_line_item"

Filter Description. The filter passes only product line items: a line whose Type is empty (null) is skipped, and a line whose Type is "promotion_line_item" is skipped. As a result, promotion lines on the Shopware deposit order are not created as Transaction Lines in iPaaS.com; order-level promotion and discount handling is applied to each line's extended price through the header-discount distribution instead. The filter does not throw an exception; non-qualifying lines simply do not pass.

Description: Child collection that transfers the deposit's qualifying line items to iPaaS.com as Transaction Lines, with the SKU, status, tax percent, and discount-distributed extended price resolved per line.

Mapping Type	Source Field (Shopware)	Destination Field (iPaaS.com)	Description
Field	UnitPrice	UnitPrice	optional — Maps the Shopware deposit line item unit price to the iPaaS.com Transaction Line unit price.
Field	Quantity	Qty	optional — Maps the Shopware deposit line item quantity to the iPaaS.com Transaction Line quantity.
Field	UnitPrice	OriginalUnitPrice	optional — Maps the Shopware deposit line item unit price to the iPaaS.com Transaction Line original unit price, preserving the pre-discount unit price for reference.
Field	Label	Description	optional — Maps the Shopware deposit line item label (its display name) to the iPaaS.com Transaction Line description.
Static	`"Product"`	Type	optional — Sets the iPaaS.com Transaction Line type to the constant value Product, identifying the row as a product line.
Dynamic Formula	Resolve SKU (see formula below)	Sku	optional — Uses the Shopware product number as the SKU, falling back to the line item label when no product number is present.
Dynamic Formula	Resolve status (see formula below)	Status	optional — Resolves the Shopware transaction state name with TransactionStateNameFromId, defaulting to Pending when the state cannot be resolved.
Dynamic Formula	Sum tax rates (see formula below)	TaxPercent	optional — Sums the absolute value of every tax rate on the line's price tax rules; returns 0 when the line has no tax rules.
Dynamic Formula	Distribute header discount (see formula below)	ExtendedPrice	optional — Sets the line total reduced by its proportional share of the deposit's header-level discount; equals the line total when there is no discount.

// Sku
if(Payload_ProductNumber!=null && Payload_ProductNumber!="")
{
    return Payload_ProductNumber;
}
return Label;

// Status
var status = await TransactionStateNameFromId(StateId);
if(!string.IsNullOrEmpty(status))
  return status;
return "Pending";

// TaxPercent
var sumofAllTaxes = Price_TaxRules.Select(x => Math.Abs(x.TaxRate)).Sum();
return sumofAllTaxes;

// ExtendedPrice
//This will distribute the total header discount amount among line items based on line extended price and ticket subtotal
var discount = await GetSumOfPromotions(Parent.Promotions);
if (discount != null && discount > 0){
    var proportion = TotalPrice / (discount + Parent.PositionPrice);
    var lineAmount = proportion * discount;
    return TotalPrice-(Math.Round(lineAmount,2));
}
return TotalPrice;

Error Handling

"Shopware API temporarily unavailable": If the Shopware API is unavailable when the deposit transfer runs, the transfer fails and an error appears in Dashboard / Integration Monitoring / Error Logs. Resolution: re-run the deposit transfer; for child records, re-trigger the parent deposit transfer.
Parent order, customer, or company not linked: When the parent order, customer, or company has not yet been transferred and linked in iPaaS.com, the corresponding identifier resolves empty and the deposit cannot be associated with it. Resolution: transfer and link the related record first, then re-run the deposit transfer.

Testing & Validation

Test Scenarios

Confirm the parent collection's filter returns false on the standard order webhook and Manual Sync paths so that no standard order event or Manual Sync entry transfers a deposit, and that the deposit flow is the only path that routes a deposit to the collection.
Transfer a deposit (Ticket) through the integration's deposit flow and confirm it is created in iPaaS.com as a Transaction of type Ticket with the expected TransactionNumber, subtotal, shipping, tax, total, total quantity, discount amount, email, status, and order date.
Confirm the deposit is linked to the correct iPaaS.com customer (individual) or company (B2B) and to its parent order, and confirm the parent link resolves only when the parent order has already been transferred and linked.
Transfer a deposit with multiple addresses and confirm each address is created with resolved Country and Region names and correct billing/shipping flags, and that the shipping method and shipping flag are empty/false when the deposit has no tracking record.
Transfer a deposit with a payment and confirm the Transaction Payment carries the resolved payment method name in both Method and Description, the resolved status, and the amount.
Transfer a deposit whose line items include a promotion line and confirm promotion lines are excluded while product lines transfer with the expected SKU, status, tax percent, and discount-distributed extended price.
Transfer a deposit with no promotions and confirm each line's extended price equals its line total, and the deposit-level discount amount is 0.

Validation Checklist

Confirm the deposit flow is enabled for the implementation before relying on deposit transfers; the parent collection does not transfer deposits on its own.
Confirm the parent order, customer, and company are transferred and linked in iPaaS.com before transferring a deposit.
Confirm the transaction type is Ticket and the TransactionNumber carries the Shopware order number ending in "-D".
Confirm the Status translation maps Done to Complete and Cancelled/Order clearance denied to Cancelled, and that non-English store languages are handled by extending the status mapping where needed.
Confirm the currency name resolves into the Shopware Currency Name custom field and the sales channel ID into the Shopware Sales Channel custom field.
Confirm each child address, payment, and line item stays associated with the deposit transaction created by the parent transfer.
If either child Add collection is later paired with an Update collection, confirm whether the unmapped fields (address: ShipDate, ShippingAmount, ShippingMethodDescription; line item: DiscountAmount, DiscountPercent, EstimatedTaxAmount, QtyShipped, Weight) need to be preserved with a DestinationValue mapping before enabling the Update path.

Additional Notes

The parent collection is intentionally disabled by default through its return false filter; deposits are added only through the integration's deposit flow. This applies at the time this documentation was written.
Standard non-deposit orders are out of scope for this family and are transferred by the Add/Update Shopware Order TO iPaaS.com collection, which excludes deposits (order numbers ending in "-D").
Deposit, address, payment, and line item deletions are not propagated by this family.
These limitations are inherent to the current design of the integration and the capabilities of the Shopware API, and they apply to all subscribers at the time this documentation was written.

Shopware to iPaaS.com Customer Mapping Documentation

Shopware to iPaaS.com Order Mapping Documentation

Shopware to iPaaS.com Order Return Mapping Documentation

Shopware Order Update From iPaaS.com Mapping Documentation

Shopware Order Return From iPaaS.com Mapping Documentation