<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>thread Re: Selling items with price embedded barcodes - different weights in Orders, Menu Items, Catalog &amp; Fulfilment</title>
    <link>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/Selling-items-with-price-embedded-barcodes-different-weights/m-p/846110#M23609</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Based on what you’ve described, it sounds like you’re using &lt;/SPAN&gt;&lt;SPAN&gt;price-embedded (or variable price/weight) barcodes&lt;/SPAN&gt;&lt;SPAN&gt;, where the first part of the barcode identifies the product and the remaining digits contain the calculated price.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;At this time, Square doesn’t natively support parsing price-embedded barcodes in the way many grocery stores, butchers, and delis use them. Square expects a barcode to match a single item in your Item Library rather than reading part of the barcode as the item ID and the remainder as the item’s price or weight.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;As a workaround, some sellers:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Sell by manually entering the weight at checkout using unit-based pricing.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Use fixed barcodes for packaged items with standard weights.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Explore third-party integrations that support variable-weight barcode workflows if this is a core part of their business.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;I know that isn’t the ideal answer, especially for businesses selling products by weight. It would be a great feature request, as support for GS1/price-embedded barcodes could make the checkout process much more efficient for sellers like yourself.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Hopefully other community members with similar workflows can share what’s worked best for them as well.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 11 Jul 2026 23:05:50 GMT</pubDate>
    <dc:creator>kacey_k</dc:creator>
    <dc:date>2026-07-11T23:05:50Z</dc:date>
    <item>
      <title>Selling items with price embedded barcodes - different weights</title>
      <link>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/Selling-items-with-price-embedded-barcodes-different-weights/m-p/846091#M23608</link>
      <description>&lt;H2&gt;&lt;FONT size="4"&gt;Would like some assistance in regards to scanning price embedded barcodes for products that have different weights?&lt;BR /&gt;&lt;BR /&gt;We sell our products by kg.&lt;BR /&gt;Some of our items have barcode labels set up and printed on a scale set up for our wholesale products.&lt;BR /&gt;Each barcode contains a 12 digit barcode number made up as below...&lt;BR /&gt;*First 6 numbers = a product number identifying the actual product (i.e 200024 - Mince) *Last 6 numbers contain the total price of the product (sold by kg when manually weighed)....e.g. 917428 (The product total is $17.42) Each packet is a different weight so the last 6 numbers vary dependent on the weight of the product.&lt;BR /&gt;We are able to scan items that have an item barcode (ie. a barcode that is the same for each product...sold as each) but unable to for weighted products.&lt;BR /&gt;Any suggestions would be greatly appreciated.&lt;BR /&gt;&lt;/FONT&gt;&lt;/H2&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 11 Jul 2026 09:09:40 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/Selling-items-with-price-embedded-barcodes-different-weights/m-p/846091#M23608</guid>
      <dc:creator>CRButchery</dc:creator>
      <dc:date>2026-07-11T09:09:40Z</dc:date>
    </item>
    <item>
      <title>Re: Selling items with price embedded barcodes - different weights</title>
      <link>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/Selling-items-with-price-embedded-barcodes-different-weights/m-p/846110#M23609</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Based on what you’ve described, it sounds like you’re using &lt;/SPAN&gt;&lt;SPAN&gt;price-embedded (or variable price/weight) barcodes&lt;/SPAN&gt;&lt;SPAN&gt;, where the first part of the barcode identifies the product and the remaining digits contain the calculated price.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;At this time, Square doesn’t natively support parsing price-embedded barcodes in the way many grocery stores, butchers, and delis use them. Square expects a barcode to match a single item in your Item Library rather than reading part of the barcode as the item ID and the remainder as the item’s price or weight.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;As a workaround, some sellers:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Sell by manually entering the weight at checkout using unit-based pricing.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Use fixed barcodes for packaged items with standard weights.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Explore third-party integrations that support variable-weight barcode workflows if this is a core part of their business.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;I know that isn’t the ideal answer, especially for businesses selling products by weight. It would be a great feature request, as support for GS1/price-embedded barcodes could make the checkout process much more efficient for sellers like yourself.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Hopefully other community members with similar workflows can share what’s worked best for them as well.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 11 Jul 2026 23:05:50 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/Selling-items-with-price-embedded-barcodes-different-weights/m-p/846110#M23609</guid>
      <dc:creator>kacey_k</dc:creator>
      <dc:date>2026-07-11T23:05:50Z</dc:date>
    </item>
  </channel>
</rss>

