# Barcode and QR code scanning support

**URL:** <https://community.fibery.io/t/barcode-and-qr-code-scanning-support/11068>\
**Category:** Ideas & Features\
**Created:** [July 15, 2026, 7:45am UTC](https://community.fibery.io/t/barcode-and-qr-code-scanning-support/11068 "2026-07-15T07:45:17Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\
**Post date:** [July 15, 2026, 7:45am UTC](https://community.fibery.io/t/barcode-and-qr-code-scanning-support/11068/1 "2026-07-15T07:45:17Z")

</div>

Hello,

Will it be possible to add the support of barcode and QR code scanning with the camera ? This should be possible with the camera of a mobile phone _(Android/iOS app)_ or with a Webcam on a desktop _(Windows app or Web app)_.

I have some use case for this :

- scan to search an entity on the entire Workspace

- trigger automations after a scan

- doing a stock inventory of articles

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [July 15, 2026, 8:01am UTC](https://community.fibery.io/t/barcode-and-qr-code-scanning-support/11068/2 "2026-07-15T08:01:16Z")

</div>

Had you seen this post:

> [@June 25, 2026 / brick Custom Apps, AI credits & extra usage, Better performance for large tables, Set static default values for basic fields, Automations history](https://community.fibery.io/t/june-25-2026-custom-apps-ai-credits-extra-usage-better-performance-for-large-tables-set-static-default-values-for-basic-fields-automations-history/11012/11):
>
> Ok, I was cautiously optimistic about the Custom Apps and figured there might be some big limitations. There still might be, but this is crazy exploding_head . I did a single, crappy, two sentence prompt to see if I could get it to pull up a camera feed for scanning QR codes. 60s later, I get this: I gave it a QR code from an entity id in a specific, prompted DB and it pulled it up instantly. A bit more tweaking …

I am imagining that most (all?) of what you need to do can be achieved with a custom app

---

<div class="post-metadata">

**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\
**Post date:** [July 15, 2026, 9:54am UTC](https://community.fibery.io/t/barcode-and-qr-code-scanning-support/11068/3 "2026-07-15T09:54:24Z")

</div>

We probably can do many things with Custom Apps and I will try to create one for what I’m looking to build. But, I agree with @helloitse when she say :

> There are a lot of exciting AI possibilities and certainly the need for agentic UIs keeps Fibery competitive. But I hope to see the velocity of core platform updates pick up in Q3.  
> There is more to Fibery outside of what costs us AI tokens to achieve and I hope a lot of the standing feature requests get to see some love.

What we want to see in Fibery is native functions and not only things based on AI build.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [July 15, 2026, 10:06am UTC](https://community.fibery.io/t/barcode-and-qr-code-scanning-support/11068/4 "2026-07-15T10:06:30Z")

</div>

I understand that, but I think the chance of native barcode support being introduced in the next 6 months is very low, so if you don’t want to wait, a custom app (built with AI or manually) might be a way to go.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [July 15, 2026, 10:12am UTC](https://community.fibery.io/t/barcode-and-qr-code-scanning-support/11068/5 "2026-07-15T10:12:10Z")

</div>

Barcode scanner request has 0 chances to be implemented. It is a very specific feature that may be useful for a very small subset of users, and if we start to add such features Fibery will be overcomplicated very fast.

The only way to solve such requests is to allow users create custom extensions. In the past it was hard, since you had to be a developer. Now the barrier is lowering and more and more people are able to build something decent. So our goal is twofold

1. Provide extensions points in Fibery where people can add custom things
2. Use AI to empower users adding custom things to these extension points

Custom Apps are the first step here, so you may indeed try to create the app (and if we have some platform limitations, we may fix them to make it work). For quick access you can add this App to favorites and overall it can provide good experience

---

<div class="post-metadata">

**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\
**Post date:** [July 15, 2026, 11:37am UTC](https://community.fibery.io/t/barcode-and-qr-code-scanning-support/11068/6 "2026-07-15T11:37:05Z")

</div>

Thanks to both of you for your feedback.

I’ve started to build the app and I admit that it is impressive. It is already working and I’m doing additional prompts to get it better. I’ve spent ~500 credits until now.

I hope Fibery evolves in a direction that gives it more flexibility to implement native functions.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [July 15, 2026, 11:39am UTC](https://community.fibery.io/t/barcode-and-qr-code-scanning-support/11068/7 "2026-07-15T11:39:13Z")

</div>

> [@Jonathan1](#):
>
> I hope Fibery evolves in a direction that gives it more flexibility to implement native functions.

This is our goal and if you hit limitations in the platform we would be happy to listen and think how to expand the platform to remove this limitation
