Splitting Line Items in Orders

Topic summary

A user seeks a way to split line items in Shopify orders so that each item appears with quantity 1 instead of grouped quantities (e.g., “Item x1” four times rather than “Item x4”). They’re looking for either:

  • An app solution to handle this automatically
  • API guidance (REST/GraphQL) to build a custom implementation
  • A method to retroactively edit existing orders

Use Case Identified:
Another user confirmed having the same need—their external services don’t support quantity fields, requiring individual line items for integration. For example, an order with 5 units of one product and 2 of another must be transmitted as 7 separate line items.

Current Workaround:
One user is temporarily storing split data in the additional_details field as JSON, though they acknowledge this adds unnecessary complexity.

Status: The discussion remains open with no definitive solution provided yet. No specific apps or API methods have been recommended.

Summarized with AI on October 27. AI used: claude-sonnet-4-5-20250929.

I would like to split line items in my orders so that quantity is always 1. Instead of having “Item x4” I want “Item x1” four times. Is it possible to edit existing orders to make this happen. Even a solution so this happens automatically to future orders would be appreciated.

I’m looking for an app to do this, but I’m comfortable with the REST and GraphQL APIs as well, so I could do it myself with some guidance.

This is not a very common request. Honestly I don’t know how much I can be of use to you on this but I would definitely like the know the reason behind it.

How and in what way does it affect your business??

@Shadab_dev i’m having the same request, the reason is that when i need to communicate with external services i need to send one by one because they don’t have support to quantity.

so if i have 2 line_items:

line_item_1: qtd 5
line_item_2: qtd 2

it needs to be splitted in 7 lines, the way i trying to that now is creating a JSON in additional_details, but is a little bit of overhead in the solution