The Rifkin Safety Sac is A. Rifkins Co's premier product... a high quality, high security night deposit bag.

Research and development have always been part of Rifkin's custom-manufacturing operation. In 1966, Rifkin developed a high security courier bag which was fire-resistant, to protect valuable documents in the case of car or truck fire.

The Rifkin Trans-Sac, a Post Office-approved, reusable roundtrip mailing envelope, was developed by and patented by A. Rifkin Co. in 1963.

 

Zipper coin bags (without locks) occupy a large part of the Rifkin manufacturing area. The popular "W" style Long Zipper Bag and "WT" style Trans-Sac, reusable mailing envelope, are currently being made by teams of workers known as modular production groups. This new concept increases Rifkin's ability to accommodate "rush" delivery requests and hold to projected delivery dates.

Originally, the varied steps required to make the Rifkin Safety Sac utilized basic sewing machines. Over the years, the procedure has changed greatly, being refined and improved by the introduction of specially designed equipment.

Today, Rifkin Safety Sacs are being manufactured by teams. When a Safety Sac team receives the embroidered or imprinted pieces of material, they move them from one operation to another, sewing the lock cover, sewing the zipper, sewing the side and bottom seams, and installing the Arcolock.

A recent innovation in the Rifkin manufacturing facility is the Lock Assembly Group. This new in-house system allows Rifkin to satisfy special needs that arise for a specific Arcolock or master keyed Arcolock number.

As the varied products are completed, they are examined, bundled, labeled and sent to the Shipping Department. There the order is packed in shipping containers and sent on its way to the customer.

Contact Us | On-Line Catalog | About Rifkin | Home

Orders and Inquiries • 570-825-9551 • Toll-Free 1-800-458-7300 • Fax: 1-800-825-8284
In Europe A.Rifkin Co Ltd. Tel: +44 (0) 1428 717 850 • Fax: +44 (0) 1428 717 950
Privacy Policy | Copyright Statement