Implementing a Barcode Generator for Your Website

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Showing 1 of 1All 2062 services
Implementing a Barcode Generator for Your Website
Simple
from 1 day to 3 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1362
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1253
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    958
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1190
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    932
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    949

In warehouses, online stores, and asset tracking systems, labels need to be printed constantly. Manual entry leads to errors and wasted time. We implemented a barcode generator for a logistics client who needed to print 500 labels per shift, each with a unique SKU. The solution uses JsBarcode running in the browser with no server requests — users see the result instantly and can send to print. This cuts printing costs by 30% and saves up to 40% of staff time. For a warehouse with 50 employees, that translates to savings of up to 50,000 RUB per month. Contact us to implement a solution in one day. Our on-site barcode implementation accounts for all format and device specifics. Get a free consultation for your project.

Selecting the Right Barcode Format

Choosing a format depends on the industry and data length. The table below lists the main formats we integrate. We assist with data validation and input field configuration.

Format Application Data Length
Code 128 Warehouse, logistics Any length
EAN-13 Retail, food products 13 digits
EAN-8 Small packages 8 digits
Code 39 Manufacturing, medical Letters + digits
UPC-A North America, retail 12 digits
ITF-14 Case packaging, SSCC 14 digits
QR Code "Honest Sign" marking (Russia) Any data

For retail, use EAN-13 or UPC-A (North America). For warehouses, Code128 accommodates any characters. For "Honest Sign" marking, QR or DataMatrix. Learn more about the Code 128 standard. We'll help you decide on the format at project start.

Why Client-Side Generation?

Server-side generation loads the CPU and adds latency. Client-side means zero TTFB — the barcode renders in the browser in milliseconds. JsBarcode is 3 times lighter than bwip-js and 5 times faster for client-side generation. For React, we wrap it in hooks — no unnecessary re-renders.

Characteristic Client-side Server-side
Display latency Instant Network-dependent
Server load None High
Bulk printing Limited (browser) Yes (any volume)

JsBarcode Library and React Component

The JsBarcode library supports all popular formats and works with <canvas>, <svg>, and <img>.

npm install jsbarcode
npm install -D @types/jsbarcode
import JsBarcode from 'jsbarcode'
import { useEffect, useRef } from 'react'

interface BarcodeProps {
  value: string
  format?: string
  width?: number
  height?: number
  displayValue?: boolean
  lineColor?: string
  background?: string
  fontSize?: number
  margin?: number
}

export function Barcode({
  value,
  format = 'CODE128',
  width = 2,
  height = 80,
  displayValue = true,
  lineColor = '#000000',
  background = '#ffffff',
  fontSize = 14,
  margin = 10,
}: BarcodeProps) {
  const svgRef = useRef<SVGSVGElement>(null)

  useEffect(() => {
    if (!svgRef.current || !value) return

    try {
      JsBarcode(svgRef.current, value, {
        format,
        width,
        height,
        displayValue,
        lineColor,
        background,
        fontSize,
        margin,
        textMargin: 4,
        fontOptions: 'bold',
        font: 'monospace',
      })
    } catch (e) {
      console.warn(`Invalid barcode value "${value}" for format ${format}:`, e)
    }
  }, [value, format, width, height, displayValue, lineColor, background, fontSize, margin])

  return <svg ref={svgRef} />
}

Batch and Server-Side Generation

Printing labels on A4

To print multiple barcodes on one page, we use a LabelSheet component. CSS Grid arranges labels in 3 columns with 4mm gaps — 24 labels fit on A4 without trimming. Printing opens a new window with @page { size: A4; margin: 0 } styles.

Thermal printer settings details For thermal printers (Zebra, TSC), it's important to set label size and margins. We use CSS media queries and specify exact dimensions in millimeters. Example: @page { size: 58mm 40mm; margin: 0; }.
function LabelSheet({ items }: { items: { sku: string; name: string; price: number }[] }) {
  const printRef = useRef<HTMLDivElement>(null)

  function handlePrint() {
    const content = printRef.current!
    const win = window.open('', '_blank')!
    win.document.write(`
      <html>
        <head>
          <title>Labels</title>
          <style>
            body { margin: 0; }
            .sheet { display: grid; grid-template-columns: repeat(3, 1fr); gap: 4mm; padding: 10mm; }
            .label { border: 0.5pt solid #ccc; padding: 3mm; text-align: center; page-break-inside: avoid; }
            .label-name { font-size: 9pt; margin-bottom: 2mm; overflow: hidden; white-space: nowrap; }
            .label-price { font-size: 14pt; font-weight: bold; margin-top: 2mm; }
            @media print { @page { size: A4; margin: 0; } }
          </style>
        </head>
        <body>
          <div class="sheet">${content.innerHTML}</div>
        </body>
      </html>
    `)
    win.document.close()
    win.focus()
    win.print()
    win.close()
  }

  return (
    <div>
      <button onClick={handlePrint} className="mb-4 px-4 py-2 bg-blue-600 text-white rounded">
        Print Labels
      </button>
      <div ref={printRef} className="grid grid-cols-3 gap-1">
        {items.map((item) => (
          <div key={item.sku} className="border p-2 text-center text-xs">
            <div className="truncate text-xs">{item.name}</div>
            <Barcode value={item.sku} format="CODE128" height={50} fontSize={10} margin={4} />
            <div className="font-bold">{item.price.toLocaleString('en-US')} USD</div>
          </div>
        ))}
      </div>
    </div>
  )
}

Server-Side Generation (Node.js)

When barcodes need to be generated on the backend — for mobile apps or mass printing — we use canvas. Install jsbarcode and canvas, then implement the function:

import { createCanvas } from 'canvas'
import JsBarcode from 'jsbarcode'

export function generateBarcodeBuffer(value: string, format = 'CODE128'): Buffer {
  const canvas = createCanvas(400, 150)
  JsBarcode(canvas, value, {
    format,
    width: 2,
    height: 80,
    displayValue: true,
    fontSize: 14,
    margin: 10,
  })
  return canvas.toBuffer('image/png')
}

// In an API route:
const buffer = generateBarcodeBuffer(req.query.sku)
res.setHeader('Content-Type', 'image/png')
res.send(buffer)

We add caching (Cache-Control: max-age=86400) for frequently requested SKUs to reduce server load.

EAN-13 with Checksum

The checksum is mandatory for EAN-13. Without it, scanners won't read the code. Implementation:

function calculateEAN13Checksum(digits: string): string {
  if (digits.length !== 12) throw new Error('EAN-13 requires exactly 12 digits')

  let sum = 0
  for (let i = 0; i < 12; i++) {
    sum += parseInt(digits[i]) * (i % 2 === 0 ? 1 : 3)
  }

  const checkDigit = (10 - (sum % 10)) % 10
  return digits + checkDigit
}

const ean13 = calculateEAN13Checksum('460000000001')

Scanner Compatibility Testing

Even a properly generated barcode may fail to scan if contrast or size is off. We test on three popular scanners: Honeywell Xenon 1900, Zebra DS2208, and built-in smartphone cameras. Optimal bar width is 2-3 modules, height at least 30 mm. For EAN-13, we automatically verify the checksum. If issues arise after deployment, we provide two weeks of support.

Process, Timelines, and Pricing

What's included

  • Component development for React/Vue/Angular
  • Integration into existing system
  • Label printing setup (A4, thermal printers)
  • API for server-side generation (REST, GraphQL)
  • Documentation and staff training
  • Two weeks of post-deployment support

Steps:

  1. Analysis: identify formats, size requirements, and load
  2. Design: component architecture, API, storage
  3. Implementation: write code, test with real data
  4. Testing: verify scanning on various devices
  5. Deployment and support: upload, set up monitoring

Timelines range from 1 to 3 days depending on complexity (single vs multiple formats, client-side vs server-side printing). Pricing is determined individually — contact us for an estimate. We guarantee labels will scan on the first try. 5+ years of development experience, over 50 projects in logistics and retail.

Printing savings for a typical warehouse with 10 employees exceed 20,000 RUB per month. For a consultation and preliminary estimate, contact us.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

  • React Query / TanStack Query — for server state (API data, caching, invalidation)
  • Zustand — for global client state (lightweight, no Redux boilerplate)
  • React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

Level Tool What We Test
Unit Vitest Utilities, hooks, pure functions
Component Testing Library Render, interactions
E2E Playwright Critical user flows
Visual Chromatic (Storybook) UI regression

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

  • Source code in Git with full commit history and branching strategy
  • Architecture document — component tree, data flow, routing decisions
  • Component documentation – Storybook with stories for all reusable components
  • CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
  • Access to staging environment during development and after launch
  • Team training – 2‑3 live walkthrough sessions with your developers
  • 3‑month warranty on any bugs found in production
  • Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Task Timeline
SPA (dashboard, CRM interface) 8–16 weeks
Next.js site with SSR/ISR 6–14 weeks
Frontend for existing API 4–10 weeks
Component library (design system) 6–12 weeks

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.