Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 1934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 2059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 2184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 2309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 2434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 2559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 2684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 2809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 2934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 3059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 3184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 3309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 3434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 3559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 3684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 3809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 3934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 4044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 4169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 4294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 4419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 4544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 4669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 4794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 4919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 5044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 5169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 5294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 5419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 5544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 5669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 5794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 5919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 6044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 6169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 6294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 6419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 6544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 6669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 6794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 6919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 7044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 7169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 7294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 7419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 7544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 7669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 7794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 7919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 8044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 8169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 8294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 8419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 8544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 8669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 8794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 8919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 9044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 9169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 9294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 9419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 9544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 9559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 9669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 9684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 9794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 9809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 9919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 9934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 10934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 11934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 12934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 13934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 14934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 15934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 16934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 17934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 18934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 19044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 19059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 19169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 19184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 19294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 19309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 19419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 19434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 19559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 19684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 19809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 19934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 20059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 20184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 20309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 20434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 20559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 20684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 20809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 20934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21434

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21544

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21559

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21669

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21684

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21794

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21809

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21919

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 21934

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 22044

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 22059

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 22169

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 22184

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 22294

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 22309

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 22419

Notice: Uninitialized string offset: 0 in /web/terminalfour/htdocs/news/archive/2018/how-durex-can-recover-from-its-product-recall.php on line 22434
Skip to content

How Durex can recover from its product recall

Published:

Dr Liz Breen looks at product recall

File 20180802 136649 1qbswbr.jpg?ixlib=rb 1.1 Shutterstock/ZoltanKiraly Liz Breen, University of Bradford

The condom maker Durex is in brand crisis mode after it was forced to issue a recall of some of its products over fears they could split. Durex is not the first company to suffer from high profile product recalls. There is no doubt that such episodes can cause lasting damage to a brand’s reputation but the fact is recalls happen. Other global brands which have gone though much bigger issues have shown that if they are dealt with quickly and appropriately, a company can survive and prosper.

The Reckitt Benckiser Group plc (RBG) (the manufacturer of Durex condoms) is the latest business to fall foul of product deficiencies. It has recalled ten batches of Durex Real Feel condoms and Durex Latex Free condoms due to a “risk that the condom might tear or leak, reducing its protection from sexually transmitted diseases and pregnancy”. Durex confirmed that “a limited number” had not passed its “stringent shelf life durability tests” and apologised.

A product recall can mean life or death to a business. Over the next few days, RBG will have to strategically coordinate how it manages the product recall to reduce any lasting damage to its reputation, brand and product value.

High profile brand issues

Product recalls are not new and occur in every sector where there is a threat to safety or life due to defective parts, unreliability of materials or quality assurance issues.

Research has shown that small companies can flounder, curl up and die with the onslaught of dealing with product recalls, customers, claims, returns and repairs. Their cash flow and infrastructure cannot cope. It becomes all too much and bankruptcy looms.

The world’s largest toy manufacturer has had to recall batches of toys over the years. Shutterstock/360b

For example, the recall of 1,000 toys cost small business owner Cynthia Thomas US$15,000 and nearly her business due to a drop in customers and sales. Larger companies cope much better as they have deeper pockets, additional, non-affected assets and an army of resources at their disposal. This is perhaps why the world’s biggest toymaker, Mattel, has coped better with a number of major recalls of Chinese-made products after lead was found in the paint of some toys.

And Durex as a brand can take comfort in the fact that the impact of product recalls is felt to be more short term than long. Companies such as Toyota and Volkswagen have demonstrated that you can face huge catastrophes, the wrath of your customers and the sector, but still regain a strong place within the market.

In 2012, Toyota had 7.43m cars recalled globally while Volkswagen had to recall 11m vehicles after it admitted cheating on US emissions tests. Both companies have managed to stay stable in the market despite the fact that their reputation has been dented on more than one occasion.

The public will always acknowledge that defective products exist, regardless of stringent operational systems, checks and balances. So what should RBG do to reduce the level of condemnation that it now faces?

Apologise quickly and take action

A company in this situation needs to act fast, taking immediate responsibility for its actions and deliver action, not rhetoric. An apology goes a long way to fixing the problem. Durex has made this important first step and said sorry to its customers and offered refunds.

The refund of product costs to customers is an expected response but the business may need to do more in order to avoid more damning repercussions – such as loss of sales, sponsorship and affiliations.

So an apology alone may not be enough. RBG will need to build up confidence in the brand through decisive action. One way to do this is to settle claims quickly. The business needs to ensure that it proactively seeks out failed products – as opposed to waiting for them to come out of the woodwork. Companies which voluntarily address this issue, as opposed to being forced to by their customers, are much more likely to retain them.

An opposing view is that the need to act quickly may be seen as an admission of guilt and inflate anxiety in the marketplace. So RBG needs to tactfully handle all communications to present a positive image to the public.

The Medicines and Healthcare products Regulatory Agency has stated that pharmaceutical wholesalers will collect damaged stock immediately from pharmacies. But customers are being asked to act responsibly and return products from their point of purchase. This can lead to a reduced number of returns as there is no collection mechanism and the customer has to make all the effort to return the product. The lure of refunded money may not be enough to make a return happen.

To address this, RBG could arrange for drop off points for the customers (convenient to them) or arrange for local collections, piggybacking on other delivery networks, like couriers, pharmaceutical wholesalers and the Royal Mail.

Looking ahead

In the future, RBG has to make its customers believe in the quality and safety of its product. For example, Rolls Royce was very transparent in its need to recall products in 2015 – even when it affected just one car, a Rolls Royce Ghost which was recalled because of a problem with the side-impact airbags. In doing so, customers were reassured that quality and safety were at the forefront of the business. RBG needs to adopt the same stance with Durex and its other products.

Condoms are a very popular product. In the Rio Olympics 2016, it was reported that the event lasted 17 days, had 10,500 athletes, 33 venues, and 450,000 condoms. The amount allocated was three times more than in the London Olympics in 2012. As a product they provide a vital public health function and provide psychological and emotional support to people using them.

The ConversationA good solid corporate reputation can withstand most business traumas. Companies in crisis have to work harder to be seen as a “good” business to buy from and trade with. RBG needs to think strategically, act responsibly and react quickly to stay in business and provide its products to the masses.

Liz Breen, Reader in Health Service Operations, University of Bradford

This article was originally published on The Conversation. Read the original article.

Back to news from 2018